Me three. I'd love to be able to install the SL3 plug in so I can view SL2 and SL3 apps, AND continue to develop my SL2 apps (current iteration will continue to be done in SL2 but once that's done we'll look at SL3). Even with us expecting the release we won't be able to switch immediately. Am pleasantly surprised at how soon SL3 has arrived so happy to use a VM. It sounds like the Dev tools are too tightly coupled with the runtime installed.
It's great having a channel that is obviously listening to feed back to! Looking at the example apps in Blend 3 and how much behaviour stuff is in there is blowing my mind... Its very cool. I'm getting a hint of what the future is going to look like, and 'tis good. :) cheers, Stephen On Sat, Jul 11, 2009 at 5:54 AM, John OBrien <[email protected]>wrote: > I agree with Craig, nice to have still have the option but looking > forward it may have confused the situation. In a few months we will all be > on SL3 and never look back. > > But I would still choose to have Silverlight3 released yesterday and have > to use a VM rather than have waited 2 more months and had it run > side-by-side. > > Rebooting back to my Vista partition to have a play... > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Craig Dunn > *Sent:* Saturday, 11 July 2009 7:18 AM > > *To:* [email protected] > *Subject:* Re: Do we upgrade to Silverlight3 on our dev machines? > > > > Thanks Scott, > > >>You can't create Silverlight 2 Projects if you install the Silverlight 3 > bits, as this has to do with the SDK's etc occupying the same spots inside > the devs computer. > yeah I can kinda understand that bit. take this as a confused/dazed query > rather than a jumping up-and-down rant. > > What I don't get is why I can't keep the SL2 DevTools but install the SL3 > Runtime. The SL3 installer (as per my blog post screenshots) errors out if > you have the SL2 DevTools -- it *seems* to me that I needed to install SL3 > DevTools to override that error. Correct? > > >>Let me know if this really impacts > It doesn't *really* impact me, as I will just continue to use a VM for > everything SL3 related. But it does mean I can't view SL3 content on my > 'main' PC until I'm prepared to lose SL2 development capability. > > At work, on the other hand, there are 25 developers some of whom are > working on an SL2 release. Obviously we aren't going to upgrade everything > to SL3 immediately (and force clients to download SL3 when they don't "need" > to) BUT we can't even download just the SL3 Runtime to do compatibility > checks without it wanting to install the DevTools as well (and losing SL2 > dev). Again, a VM will get around this, but it feels counter-intuitive... > > I'm repeating myself a bit here - I can imagine there are lots of > scenarios (debugging probably) that come into play - but at the end of the > day we're basically talking about a browser plugin and I don't see why my > browser can't know about SL3 while VS continues to use SL2 SDK... > > Anyway, whinging aside, I love SL3 and the speed with which it's come to > market. As content-publishers, however, we are still wary of being the > 'first' site to force a download on a customer and will want to publish > SL2-level apps for some undetermined period. > > Thanks > cd > > > On Fri, Jul 10, 2009 at 10:45 PM, Scott Barnes <[email protected]> > wrote: > > You can't create Silverlight 2 Projects if you install the Silverlight 3 > bits, as this has to do with the SDK's etc occupying the same spots inside > the devs computer. We wanted to have side by side installations of each > version but with VS2008 it was somewhat harder to implement than first > thought. Let me know if this really impacts you and specifically how, as > it's not really been a hot topic so if it's something that bugs you, rant > away at me as i'm more than happy to take this to the team in Silverlight > vNext. > > > > You can however run existing SL2 .xaps etc in Silverlight 3 as we'll make > sure the runtime itself is backwards compatible. > > > > Thx. > > > > Scott. > > > > > ------------------------------ > > *From:* [email protected] [[email protected]] > On Behalf Of Craig Dunn [[email protected]] > *Sent:* Friday, 10 July 2009 3:11 AM > *To:* [email protected] > *Subject:* Re: Do we upgrade to Silverlight3 on our dev machines? > > Silverlight 3.0 release > notes<http://go.microsoft.com/fwlink/?LinkId=157632>from > http://silverlight.net/GetStarted/ says > > *Silverlight 3 Tools and Silverlight 2 Compatibility* > Silverlight 2 projects cannot be created with the Silverlight 3 Tools for > Visual Studio 2008. To create Silveright 2 projects, uninstall the > Silverlight 3 runtime and the Silverlight 3 Tools from Add or Remove > Programs and re-install the Silverlight 2 Tools for Visual Studio 2008. > > The SL3 Tools download > page<http://www.microsoft.com/downloads/details.aspx?familyid=9442b0f2-7465-417a-88f3-5e7b5409e9dd&displaylang=en>doesn't > really say either way... > > BUT it seems that I can't even view > 3.0<http://conceptdev.blogspot.com/2009/07/silverlight-30-cant-upgrade-runtime.html>unless > I > *do *install the tools (over the 2.0 tools) > > Catch-22? > > Like I said in my blog, I don't want to be website forcing the 4Mb download > until I absolutely have to... so will probably be SL2 dev'ing for a little > while yet. Back to a VM for all 3.0 work & testing. > > I can 'kinda' understand MS' approach... but then again kinda not... did I > miss something? > > On Fri, Jul 10, 2009 at 6:49 PM, Ross McKinnon < > [email protected]> wrote: > > Scott says, its all backwards compatible, so you should be ok. But we might > have had a few, so, use your own judgement.... > > > -----Original Message----- > From: John OBrien <[email protected]> > Sent: Friday, 10 July 2009 6:34 PM > To: [email protected] <[email protected]> > Subject: Do we upgrade to Silverlight3 on our dev machines? > > It's getting late on Friday I know but did I miss a post about what happens > when we upgrade to Silverlight3 as developers? It's awesome that the > runtime > is backwards compatible so existing sites won't break but... > > > > 1) Can we still target Silverlight2 in Visual Studio? > > 2) What happens to our corporate clients without admin rights, do we > need to get their IT guys to update? > > > > John. > > > > > > > -------------------------------------------------------------------------------- > Support procedure: https://www.codify.com/lists/support > List address: [email protected] > Subscribe: [email protected] > Unsubscribe: [email protected] > List FAQ: http://www.codify.com/lists/ozsilverlight > Other lists you might want to join: http://www.codify.com/lists > > > -------------------------------------------------------------------------------- > > Support procedure: https://www.codify.com/lists/support > List address: [email protected] > Subscribe: [email protected] > Unsubscribe: [email protected] > List FAQ: http://www.codify.com/lists/ozsilverlight > Other lists you might want to join: http://www.codify.com/lists > > > ------------------------------ > > Support procedure: https://www.codify.com/lists/support > List address: > > [email protected] > > > Subscribe: [email protected] > Unsubscribe: [email protected] > List FAQ: http://www.codify.com/lists/ozsilverlight > Other lists you might want to join: http://www.codify.com/lists > ------------------------------ > > Support procedure: https://www.codify.com/lists/support > List address: [email protected] > Subscribe: [email protected] > Unsubscribe: [email protected] > List FAQ: http://www.codify.com/lists/ozsilverlight > Other lists you might want to join: http://www.codify.com/lists > > > ------------------------------ > > Support procedure: https://www.codify.com/lists/support > List address: [email protected] > Subscribe: [email protected] > Unsubscribe: [email protected] > List FAQ: http://www.codify.com/lists/ozsilverlight > Other lists you might want to join: http://www.codify.com/lists > ------------------------------ > Support procedure: https://www.codify.com/lists/support > List address: > [email protected] > > Subscribe: [email protected] > Unsubscribe: [email protected] > List FAQ: http://www.codify.com/lists/ozsilverlight > Other lists you might want to join: http://www.codify.com/lists > -------------------------------------------------------------------------------- Support procedure: https://www.codify.com/lists/support List address: [email protected] Subscribe: [email protected] Unsubscribe: [email protected] List FAQ: http://www.codify.com/lists/ozsilverlight Other lists you might want to join: http://www.codify.com/lists
