By StarkMike - 11/30/2006
I cant seem to find where I would change my visual basic 2005 project into a release build. I'm so embarrased. 
|
By StrataFrame Team - 11/30/2006
Don't feel bad... it took me forever to figure that one out as well... VS2005 kinda hides the options be default. The best way I have found is to use:Tools -> Options -> Projects and Solutions -> Check the "Show advanced build configurations" and click OK. You should then have a drop down on one of your toolbars in VS that will let you swap between Debug and Release (and any other configurations you have created).
|
By StrataFrame Team - 11/30/2006
I think you can also right-click on your solution node in the Solution Explorer and select "Configuration Manager..." from the menu. Then, you can set the active solution configuration.
|
By StarkMike - 11/30/2006
Wow. Thanks. I kinda feel guilty getting an answer to a hard-to-find question like that for free.  Kinda. HA HA
|
By StrataFrame Team - 11/30/2006
Ah, I always mooch when I can 
|
By StarkMike - 2/2/2007
Here's an interesting twist. I changed my project a release build to test something and now I cant change it back to debug. Any idea why? 
|
By Trent L. Taylor - 2/2/2007
Try cleaning your solution. Right-click on the solution and then click "Clean Solution." If this doesn't work then make sure everything is checked in and then delete the source from your local mahcine and then download it again from source control.
|
By StarkMike - 2/2/2007
Thanks. I cleaned my solution and then set the configuration option to Debug. I then built the solution, ran it and re-opened the project properties tab. It was set back to Active (Release). And  I...don't...use...source...control... 
|
By Trent L. Taylor - 2/2/2007
Uh oh ... well, let me go ahead and tell you what you knew was already coming....you need to work through source control!!!! There are so many benefits to using source control that it is hard to find a starting point. We highly recommend Team Foundation server, but even Source Safe is dramatically better than nothing at all!!!OK...so next, is source code on a network or local drive? The problem you are running into sounds like residual environment settings hanging around. Source control would help resolve this issue. Also, you should really never work off of a network drive. I know that you can adjust the machine trusts and policies to allow this to run, but I HIGHLY recommend not doing this.
|
By StarkMike - 2/2/2007
The source code is on my local drive.And yeah i knew i had that coming about source control.  I should probably look into SourceSafe. I've never been sure whether its a good product or just a program thrown together they could include as a value-add.
|
By Trent L. Taylor - 2/2/2007
Well, it is nowhere as good as Team Foundation Server, but it is definitely better than nothing...and it is free. We used it before Team Foundation was available and we have a large number of users who use VSS still. So you really need to look into moving this direction.
|
By StarkMike - 2/2/2007
Ok. Thanks for the nudge. Team foundation server means i need another *more expensive* version of Visual Studio... correct? And would a product like that be feasable for only three programmers?
|
By Trent L. Taylor - 2/2/2007
Well, if you are MSDN subscribers you can get the Workgroup edition which will support 5 developers. And yes, it is definitely worth it is you even have 2 developers. It does a lot more than source control!!!!
|
By StarkMike - 2/2/2007
We are MSDN subscribers so now I guess I have no reason not to look into it. ;-)Thanks again.
|
By Ivan George Borges - 2/2/2007
Trent L. Taylor (02/02/2007)
Well, if you are MSDN subscribers you can get the Workgroup edition which will support 5 developers. And yes, it is definitely worth it is you even have 2 developers. It does a lot more than source control!!!!Hi Trent. We also are MSDN subscribers, but the Visual Studio with Premium MSDN. Didn't know we could get the TS for 5 users!!! Thought it was a higher level of subscription! Will check that.
|
By Trent L. Taylor - 2/2/2007
Ivan,You are right. You may have to upgrade your current level of MSDN to include the Team Foundation source, but it is worth the money difference. Obviously you will have to contact Microsoft, but I think the MSDN subscription with Team Foundation Workgroup is around $2500 annually.
|