vwd.webinfo 9

Aarrghh.. I keep getting a vwd.webinfo-file added to some of my websites. According to this post on the ASP.NET forums, this file was previously known as vwdsettings.xml and contains information about what services to start in order for the web app to build and run properly. Now, to my knowledge I don’t need any services at all to be started, but I just can’t get rid of the bloody file.. One odd thing is that it only gets added when I close the solution..

I finally traced its origins to my installation of Visual Studio 2005 SDK (the June 2006 release). It seems to have something to do with the text templating engine, though I’m not even sure what that is.. Unfortunately, the problem didn’t go away even after uninstalling the SDK. I had to manually remove the file (both from source control AND the local web folder) AND also walk through all .csproj files and remove all references to it there:

<ItemGroup> <Service Include=”{B4F97281-0DBD-4835-9ED8-7DFB966E87FF}” /> </ItemGroup>

9 thoughts on “vwd.webinfo

  1. Mohsen Nov 23,2006 21:07

    Hello
    Did you find any way to turn it off?

  2. anders Nov 27,2006 12:28

    No, but I haven’t tried any of the latest VS SDKs, so I don’t know if it’s been fixed in the later versions.

  3. Jouke Dec 7,2006 08:51

    Probably repaired in December CTP of VS SDK according to: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=954064&SiteID=1

  4. Jonas Martinsson Feb 13,2007 13:02

    The bug is still there in the December CTP…

  5. MS Fanboy Mar 21,2007 05:26

    Once again… Thanks for nothing Microsoft.

    Tried the SDK uninstall – no good.
    Tried the hack the project file fix – no good (ASP.NET 2.0 don’t even have a proj file anymore).

    Went to Tools-Options.
    Went to Text Templating Node and set turned restrict mode on (restrict generation to files in the include list).

    Visual Studio Crashed.
    Restarted Visual Studio.
    Visual Studio complained that it couldn’t load the Text Templating assembly.
    Clicked OK to confirm that I want to skip loading this sh*t in the future.

    Project loaded with junk file gone.
    Not getting the SOB file added anymore.

    My love to all in the MS Visual Studio team. See you in hell.

  6. Chris Sep 11,2007 23:38

    Same problem here. Have a ASP.NET 2.0 project in source safe. I don’t recall installing the VS 2005 SDK, but I started getting this file added to the project at some point. Even though I’ve deleted it a hundred times, it just seems to get readded when you load the project again.

    What I think actually happens is VS2005 adds the file to the directory when you *close* VS. When you load the project again it’s already there and VS starts the service indicated in the vwd.webinfo file. While the service is running, even if you delete the file, it will re-add it when you close VS again. (Because Microsoft knows best, right?)

    What worked for me is close VS2005 then use Explorer to browse to your project location and delete the file. Never saw it again.

    I also deleted the registry key that it was referring to. Not sure if that helped or not, but everything still works. 🙂

  7. huaming Aug 13,2009 07:04

    This file just be created by VS when you close VS, so you must close VS first and then use Explorer to browse to your project location and delete the file.

  8. kh Aug 28,2009 11:05

    Same problem here. Have a ASP.NET 2.0 project in source safe. I don’t recall installing the VS 2005 SDK, but I started getting this file added to the project at some point. Even though I’ve deleted it a hundred times, it just seems to get readded when you load the project again.

    What I think actually happens is VS2005 adds the file to the directory when you *close* VS. When you load the project again it’s already there and VS starts the service indicated in the vwd.webinfo file. While the service is running, even if you delete the file, it will re-add it when you close VS again. (Because Microsoft knows best, right?)

    What worked for me is close VS2005 then use Explorer to browse to your project location and delete the file. Never saw it again.

    I also deleted the registry key that it was referring to. Not sure if that helped or not, but everything still works. 🙂

  9. Kyralessa Mar 25,2010 14:50

    I finally got it to go away, but in the end I had to use the two GUIDs from this page:

    http://atakala.com/browser/Item.aspx?user_id=amos&dict_id=1857

    I went through the registry and deleted *every* instance of those two GUIDs, no matter where it occurred. I also rebooted, and at least once I killed VS through the task manager (after the offending solution was loaded, but before closing it). I don’t know which of these steps helped, but I no longer have the problem, finally.

Comments are closed.