Although it’s recommended that we install Visual Studio versions in the order in which they were released (for example, install Visual Studio 2012 before we install Visual Studio 2013) as mentioned in http://msdn.microsoft.com/en-us/library/ms246609.aspx, there is possibility that we have installed Visual Studio 2013 before we know that we need to install Visual Studio 2012.
It happened to me last month. I actually more than happy to have Visual Studio 2013 only in my computer as I can also use it to open Visual Studio 2012 projects. But in the end I need to install Visual Studio 2012 because one of my teams are using Visual Studio 2012 and I don’t want any incompatibilities or project upgrades affect them.
If you have to install Visual Studio 2012 after Visual Studio 2013 for any reason, don’t worry, it can be installed without any issue.
I have been using this configuration almost a month and there is no issue at all. I mostly use them to do ASP.NET projects (and related, such as class library, etc) and I’m sure there is no issue with other project types too.
I recently upgrading ASP.NET MVC 2 solution from Visual Studio 2008 to Visual Studio 2010 (Ultimate Edition). I found that debugging was very slow. Depending on project size, it took around 30 seconds to initialize and another 5 seconds on each page request in my experience.
This kind of tool is not new. Many 3rd party software companies has built similar tool and my favorite was Iron Speed Designer but the output is ASP.NET website rather than WPF or Silverlight.
Iron Speed Designer was great. I used that tool in 2007 to 2009 because it was the main dev tool at the company I used to work. But the downside is the cost. It’s too expensive to get the full features. For a single seat of Enterprise Edition it cost $3,975.
This Visual Studio LightSwitch is absolutely a great tool and it absolutely has good market prospect. It’s a very good decision from Microsoft to develop this tool.
I hope Microsoft can release this tool in an affordable price. If that will happen, I can say “Visual Studio LightSwitch is Iron Speed Designer KILLER”.
PS: The free public beta will be available on 23 August 2010.
Changing default browser used in debugging ASP.NET MVC 2 is a bit tricky in Visual Studio 2010. To use ScottGu’s steps, you will need to add new ASPX page first. But unfortunately if you delete the page then close the application, anytime you rerun the application then the change you did will lost (it backs to use the default browser set in OS).
In my case I have Firefox set as my default browser but I need to use Internet Explorer as default browser for debugging. The trick I do is by doing these:
Open the project properties
Go to Web tab
Set the Start Action to use Start external program and then pass the Internet Explorer executable path and the url as Command line arguments.
Set the Servers’ specific port to the same port set in the url in step 3.
In my previous blog post I wrote that the requirement to enable multi-targeting feature in Visual Studio 2010 is .NET Framework 3.5 SP1 installed in the machine. But why does it not enable the Target Framework dropdown in File -> New -> Project / Web Site dialog of Visual Studio 2010 Express edition? Is multi-targeting not supported in Visual Studio 2010 Express edition?
Visual C# 2010 Express
Visual Web Developer 2010 Express
If you’re a Visual Studio 2010 Express edition user, unfortunately you cannot take advantage of the Target Framework dropdown in the File -> New -> Project / Web Site dialog (as specified in http://msdn.microsoft.com/en-us/library/bb398197.aspx). But it doesn’t mean that multi-targeting is not supported.
By default Visual Studio 2010 Express edition will create the projects with .NET Framework 4 targeted. To change the target framework you can do it from Project Properties (Solution Explorer -> [right click your project] -> Properties)