"jaems" <ja***@ntlworld.comwrote in message
news:sF*******************@newsfe1-gui.ntli.net...
When I upgrade from VS 2005 to VS 2008 and then run VS 2008 linked to my
remote website:
1) what is it doing to my website when the wizard upgrades my site?
Is it only changing the web.config file?
No, it also dinks with a few other files. If there is a .sln file out there,
that is where most of the work is being done. It will also make the website
a 3.5 version website.
Ist it reversable?
Yes, but automatically, no. But, you can reverse it if you know what you are
doing. It requires editing the files. I would agree with Scott that you
should use the backup function, or back the site up on your own. Even then,
you may have to go into IIS and change to 2.0 if you do not want to be 3.5
any more.
2) when my site has been upgraded then why does VS 2008 want to download
loads & loads of XML files before it gets started on the page I wish to
edit? VS 2005 seemed much faster in starting up
I am not sure what is going on here and will have to research this. One
thing I do know that may work slower here is Resharper, a third party plug
in, although I have not really timed it. Can you give more information about
what exactly is happening and any plug ins you might have in your
environment.
Overall, I find 2008 faster, although there are a few times that is not the
case.
3) If I have upgraded my site with the VS 2008 wizard will it screw it up
totally if I use VS 2005 to edit the site again?
I have not experienced this when I have experimented on it (last few weeks),
but you will have to have separate .sln files saved to get to the site and
common sense says you should leave the site as a 2.0 site (configurable in
both IIS and VS 2008).
--
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA
*************************************************
| Think outside the box!
|
*************************************************
