Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Want to tell us about your cool / not so cool experiences with deployment of your apps? Then go here and let us know what you think so we can improve the experience:
Technorati Tags: visual studio 2008, deployment, experiences
Comments
Anonymous
December 05, 2007
Want to tell us about your cool / not so cool experiences with deployment of your apps? Then go hereAnonymous
December 05, 2007
I have attempted to install VS2008 on my old laptop [XP] with VS 2005. I didn't have space for both so I removed the VS2005 and .Net 2.0. Well VS2008 keeps failing on the .net 3.5 Framework and never gets passed that timeframe.Anonymous
December 05, 2007
make sure to let the folks know at the link in the inital post but also gimme a shout if you can't find a resoultion in short orderAnonymous
December 06, 2007
I installed it on 64-bit Vista to do both 32-bit and 64-bit application development. We have a large C++/MFC based application that is currently built in VS2005. I am still in the process of converting it to use VS2008. We have many COM objects (DLL/OCX). We had set those to register after linking (setting on the project properties Link page). That no longer works. I believe it is because VS2008 is not elevated, but regsvr32 (or whatever VS2008 uses) requires elevation. We had created a snippet XML file that set the elevation for some of our applications to run elevated. We were importing that into the manifest file (Project Properties | Manifest section). This was because there wasn't a setting for it in VS2005 and because it would be easier to update that one file once all our applications can run AsInvoker. Now, on VS2008, it has that setting and insists on using it. So, we can no longer import that file as it conflicts with the project properties (error setting the same tag). This is kind of a bummer because we will have to change all the projects rather than one file once our application no longer requires elevation. As far as code, I've had a couple issues with some OLE DB derived classes we use, but so far, I've had no other problems converting the code to VS2008. The IDE definitely "feels" faster. Not sure about the compiling yet, but it certainly doesn't seem slower. All and all, I've been pleased and have recommended that our dev team move to VS2008.Anonymous
December 06, 2007
installation really messed up vs 2005. From what i heard .net 3.5 are simply new assemblies but apparently after installing .net framework 3.5 it ugraded .net 2.0 runtime assemblies and broke the existing apps on production. which were referencing com interopability library in .net 2.0. Hopefully someone can guide me once i give the exact error.Anonymous
December 09, 2007
The comment has been removed