Stop DB Project Launching by default when hit F5. - visual-studio-2010

Using: MVC3, Vs2010, and a DbProject
In a Solution I have an MVC3 project and a DB project. Whenever I hit f5 to startup the MVC project, the DBproject starts before. I dont want this behavior. I just want to launch the MVC project and not both projects.
The MVC project its set up as start up project.
Any Ideas?

Right click the solution and select configuration manager. Then uncheck the DB Project for the build configurations you need.

Related

"Set as StartUp Project" not changing deploy configuration in Visual Studio

I'm working at a colleagues PC. When I right click on a .Net Gadgeteer 4.2 project in our solution and select "Set as StartUp Project" I expect Visual Studio to set the build configurations so that the new start-up project is deployed to the device on start, as it does on my PC. But instead I need to open the configuration manager and manually deselect the previous start-up project and select the new one. Why? How can I swap (back) to using Visual Studio to manage deployment without the additional step in the configuration manager?
========== EDIT ==========
#john-saunders comment below makes me think I've misworded my question.
I have a solution containing multiple projects, many of which are .Net Gadgeteer projects.
On most of my machines if I right click on Project A in the Solution Explorer and select Set as StartUp Project then when I debug the solution (i.e. hit F5) Project A and any of its required dependencies are built and deployed to the Gadgeteer device and the debugger gets attached. If I then right click on Project B in the Solution Explorer and select Set as StartUp Project then when I debug the solution Project B and any of its required dependencies are built and deployed to the Gadgeteer device.
But on one machine this is not happening. Instead when I right click on Project B in the Solution Explorer and select Set as StartUp Project when I debug the solution Project A is deployed to the Gadgeteer device. To ensure that Project B is instead deployed I have to manually edit the configuration.
Why? How do I get this one machine to behave like the others?

Set project as startup in project group

I am using microsoft visual basic to create a VB6 application. Application is basically a usercontrol. I have a form in the applicaton.
What i need to do is as we do in Visual Studio 2008 add a new project in the same solution and set the project as a startup project ?
In VB6 You can have Project Groups (similar to solutions in Visual Studio .NET)
Project Groups contain usually two or more VB6 projects and have the extension .vbg
To create a project group open up one project, Click File>Add Project and add a second project. When you click on save you will be prompted to save the Project Group File.
To specify one project as the startup project right click on the project and select Set as Start Up
Once you've added the new project, right click on it, an go to properties, where you'll have a form as shown below;
As you can see in the image, you've got the Start up option, where you can just drop it down and choose form to start up.
For setting a PROJECT as start up, you can simply Right-click on the corresponding form select Set as Start Up from the context menu.
Visual Basic displays the startup project's name in bold type in the Project window.

Change start up project in visual studio 2010

I have 2 project in my solution explorer that one of this related to windows and other related to web,now i want to run web project but it runs in windows form so i want to know how to change the control to run the web project?
you need to make the web project the start up project. Right click on the web project and choose the Set As StartUp Project.

"Calls to the web service will fail unless the Silverlight project is hosted in and launched from the same web project"

I have Downloaded demo project from here
I tried to run Silverlight project SkiResult.ThinClient from the “Solution Explorer” I have configured the database nicely as SkiResult.FullClient a WPF Project works fine and display data.
But whenever I have tried to run Silverlight project in my Solution Explorer it shows me following error message.
I have googled so much I have also found one solution that set xyz.WEB project as a Start Up Project but as u can see from below screenshot of my Solution Explorer there is no xyz.WEB project in solution.
Thank you so much.....
Try setting the SkiResult.DataService project to be the startup project. This looks very much a web project created to host a Silverlight application because:
it has a Web.config file (so it is clearly a web project)
it has a Silverlight.js file (some utility JavaScript used with Silverlight),
it has some autogenerated test pages,
it has a ClientBin folder, which is typically where the compiled Silverlight application will be copied to.
When you create a Silverlight project, Visual Studio offers to create a web application project to host the Silverlight application for you. (You don't have to create a web application - VS can generate a test webpage during the build process and use that instead.) If your Silverlight project is called Xyz, then this web application will be called Xyz.Web. However, with the solution you're dealing with above, it seems this project has been renamed from the default.

Visual Studio 2010 gets stuck with solution with MVC3 Razor and Azure

I've a solution with several .dll projects, an Asp.NET MVC3 Razor project and an Cloud project.
If I try to compile the solution with the Cloud project loaded, VS2010 gets stuck in "Buil started".
I have to forcefully close VS2010 killing the process and restart. Then the compiling works good once, the next time it will get stuck again.
If I unload the project and set the mvc project as start-up, everything works (but azure of course).
What could be the problem?
Cheers.
Was it by any chance an ASP.NET MVC project to which you added a CloudService project later on or did you start off with a CloudService from the very beginning?
I was in the former situation and I had no end of problems, like not being able to open property pages or deploying the application. It's not quite your issue, but the following article might help:
http://tomkrueger.wordpress.com/2010/07/27/azure-deployment-issue-after-upgrading-to-visual-studio-2010-and-net-4-0/
As I say, my problems started because I actually added an Azure project to an existing ASP.NET MVC solution and there were some unnecessary settings left over in the web.csproj file.
All I had to do was open web.csproj in notepad and remove all occurrences of the <PlatformTarget> element.
My MVC prjoject was x86 and of course Azure works on x64 only. Even though I had the platform target set up as AnyCPU somehow Azure couldn't quite get along with it.
Maybe cleaning up your project files helps as well.

Resources