Cheryl on the Web

About the small things in life that seem oh so big

Tech Talk: VS2005 Web Deploy

Posted in Tech Talk by Cheryl on 18 September 2006

With this post I am inaugurating a new category on my blog: Tech Talk. For those of you less technically inclined (or not at all) you will have to disregard these posts I’m afraid. However, I can’t honestly contribute to the wealth of “talk” on the Web without including my 2 cents about the technology with which I work each day.

Today’s topic: deploying a web project built in Visual Studio 2005 (VS2005) - a first look. In good ole VS2003, you simply needed to build your project and copy-paste, tuh-duh! It worked. I went to deploy my first website today built in VS2005 and what a NIGHTmare! Turns out Microsoft did such a poor job of putting VS2005 together that I require a plug-in from their website even to be able to properly deploy my website. Got the plug-in, but it includes all kind of junk in the files it prepares for deployment. Altered the files the plugin includes for deployment, and that sent my VS2005 spinning out of control - anyone familiar with “Not Responding”? Ten minutes later my computer responded to my repeated “End Now” commands, and like a dummy I opened VS2005 right up again and tried to load my deploy project - same results of course.

It’s late and my muscles are sore from typing so I’ve give up for now - junk files will just get deployed I guess. I find it so peaceful to say goodnight to all - from my Mac and not my PC!

2 Responses to 'Tech Talk: VS2005 Web Deploy'

Subscribe to comments with RSS

  1. Eric said,

    on September 27th, 2006 at 17:56

    wowww, makes me wonder why you switched to VS2005 at all?? switch back! quick!

  2. Cheryl said,

    on November 24th, 2007 at 10:29

    For those that must have endings to every story: I eventually got this working. There was a bug in the ExcludeFile configuration option when Microsoft released this that resulted in infinite loops when loading the project. SP1 fixed it at a later date, but even without that I finally got this working by removing nested virtual directories from my IIS setup.

Leave a Reply