web-deployment-project

For our VB.NET websites we use SVN for Source Control and CruiseControl.NET for continuous integration. To use the SVN build number in the compilation by CruiseControl.NET we need to use Web Deployment Projects. We then replace in the configuration file the Version field with this variable from SVN Labeller $(CCNetLabel) This works great but my problem is that this variable causes warnings in Visual Studio for the solution. I'm working to remove all warnings and am left with just these two: Warning 1 The version string specified for 'AssemblyFileVersion' in the project file is invalid. C:

I've read through many of the other questions posted on the same issue, but I still do not understand the cause and how to prevent it from happening. In my case, this happens on the production server. I get the same error that has been described in other questions, and I resolve it by re-copying the assemblies into the bin directory. They are not even recompiled files, they are the same ones that were in there before - copied in again, and then it starts working without problems. The weird part of it is that I am using Web Deployment Projects to rename all of my assembly files into folder

I'm using a web deployment project in order to precompile my ASP.NET 3.5 web project . It creates a single extra DLL for the code in aspx and ascx files. And, for every aspx file there is a placeholder aspx file (empty) which needs to be copied to the server. I'd like to simplify the deployment process. Is there a way (configuring the IIS site and adding some sort of http handlers etc.) to get rid of these aspx placeholders ? Also, I'd like to know if there is a way to get rid of the .compiled files in the bin folder. It would make the deployment process smoother. Thanks! splattne I discovered

I'm working on a web project but I have this really annoying issue with my browser, Google Chrome... Everytime I make changes on my website, my browser won't refresh and clear cache. It works totally fine in my friends Chrome browser, but not for me apparently. As mentioned ctrl + F5 does not work for me. I tried to press F12 (for developer console) and right click on the refresh icon, and then click "Empty Cache and Hard Reload". Still doesn't work... Actually not true, it worked once - but now it stays the same again... I tried reinstalling chrome too, still didn't work... I tried to clear

I have finally finished my web site. I published it, and I was surprised at the results. Although the App_Code compiled into a single DLL file, every page's code behind compiled into its own DLL file. How do I make it so that it is one DLL file? Also, is it possible to compile everything (SubSonic, AJAX, etc.) into that same single DLL file? You might prefer to use the web application project style for that. You can use ILMerge to merge assemblies into one. The way we do it is by adding a deployment project to our site: http://msdn.microsoft.com/en-us/asp.net/aa336619.aspx Mitchel Sellers To

If you have an ASP.NET Web Site project type (the one without a proper .csproj or .vpproj project file and that is just a folder of loose files), then when you add a package with NuGet, it makes a *.dll.refresh file in the Bin directory to reference the package's dll in the parent packages folder. For example, if you execute "install-package elmah" from the Package Manager Console, then Elmah is placed in the packages folder in the project's solution directory, and the file Elmah.dll.refresh is placed in the project's Bin folder. When I build the project locally, Visual Studio automatically

This question already has an answer here: Pros and cons of AppSettings vs applicationSettings (.NET app.config / Web.config) 5 answers I've got some questions about two ways to save settings in the web.config. Appsettings : Look in web.config <appSettings> <add key="key1" value="value1"/> <add key="key2" value="value2"/> </appSettings> Usage in code-behind : ConfigurationManager.AppSettings["key1"]; ApplicationSettings/ Properties (autogenerated by using the 'properties'-tab in the project) Look in web.config <applicationSettings> <Projectname.Properties.Settings> <setting name=