I'm struggling to get web.config transformations working with automated builds. We have a reasonably large solution, containing one ASP.NET web application and eight class libraries. We have three developers working on the project and, up to now, each has "published" the solution to a local folder then used file copy to deploy to a test server. I'm trying to put an automated build/deploy solution in place using TFS 2010. I created a build definition and added a call to msdeploy.exe in the build process template, to get the application deployed to the test server. So far, so good!
I then tried to implement web.config transforms and I just can't get them to work. If I build and publish locally on my PC, the "publish" folder has the correct, transformed web.config file. Using team build, the transformation just does not happen, and I just have the base web.config file. I tried adding a post-build step in the web application's project file, as others have suggested, similar to:
but this fails beacuse the source web.config file has an "applicationSettings" section. I get the error Could not find schema information for the element 'applicationSettings'.I've seen suggstions around adding arguments to the MSBuild task in the build definition like
/t:TransformWebConfig /p:Configuration=Debug
But this falls over when the class library projects are built, presumably because they don't have a web.config file.
I am working on an ASP.NET project in Visual Studio .NET 2010 and attempting to make an MSI installer using a Web Setup Project. I added the Primary output from the project (which seems to pull in the relevant dependencies) and the Content Files from the project (which pulls in the Web.config and the .svc files).
The issue is that rather than applying the XDT transform and creating the Web.config using the Web.Release.config, it just copies the Web.config, the Web.Release.config, and the Web.Debug.config into the installer without doing any transformation at all.
How do I get it to apply the Web.config transformation before creating the installer?
I just used the wonderful tool Microsoft Ajax Minifier and it's working very well when I build my MVC application on my machine but when I check-in in source control and started build by the Team Build 2010 it doesn't create the min files, for sure I can't put the mini files inside the source control as the recommendation from the Microsoft Ajax Minifier because it's like the dll it's generated every time you build your application so no need to put it in source control beside it can't be because you will need always to check-out this file to build and this will prevent other from build using the team build, so what I need to do to make generate the mini file with team build 2010?
I am just starting my first MVC Web Application and have noticed that I now not only have a Web.config file in the root, but 2 sub-files, for Debug and Release configurations. I've read up a bit on what this is, in that I can put specific configurations for my different environments in each file, but I am confused as to when these seperate files are actually used.
Do I HAVE to use the built in Deployment/Publish tools within Visual Studio in order to benefit from this, or, if I set my build mode to Release, and do a simple build of my web application, then deploy the compiled files, along with the Web.config AND Web.Release.config, would that work?
I'm just not sure what deployment options I have to take advantage of these seperate config files?
I am currently trying to publish a web application in TestRelease mode and when I do, the following dll is compiled and put into the bin folder.Microsoft.VisualStudio.Settings.dll.I do not get this dll when I comple in release or debug mode so wondered if there is a setting I can change so this dll does not appear in the bin folder when I compile in TestRelease or TestDebug mode ?When I get that dll in the bin folder and try to deploy the application to our test server, I receive the following message: Could not load file or assembly 'Microsoft.VisualStudio.Settings.dll' or one of its dependencies.Any suggestions on why that dll appears in the bin folder and how I can prevent it from being deployed when I pusblish through visual studio ?
I'm using the web.config transformations on an ASP.NET site so I have .config settings for dev, test, and release environments. I need to run the source code in Visual Studio against the test database using the settings in Web.Test.config and I can't figure out how to do it. I tried changing the configuration to Test but it still uses the base Web.config settings.
I have a web application that has some non-web projects as well. When using Web Deployment, a single assembly is generated for all the aspx.vb files. When using Team Build (TS 2008), a lot number App_Web_xxx.dll file(s) are generated instead of a single assembly. How can i solve this problem and change the TFSBuild.proj file so that it can generate a single Web Assembly instead of a lot number of assemblies.
I guess thats because the MERGE operation is not occurring like it used to happen for Web Deployment Project in my solution. How can i enable MERGE of App_web_*.dll files into a single Web.dll assembly file and delete the satellite assemblies? Here is my code from TFSBuild.proj file: (MY web project is in Release|.NET Config and all other projects within the solution are in Release|Any CPU)
I have been ising TFS 2010 with VS 2010 Ultimately for a couple of months now. I have a client who is using Visual Web 2010, does anyone know if this integrated with TFS easily?
I installed a basic TFS 2010 instance on a Windows Server 2008 32bit VM. I didn't need SSRS or WSS so I left those unconfigured.
It works fine when I'm on our local network but how do I get the default TFS website [URL] to be accessible over the internet when I'm not on our local network? I'd also like for off-site members to be able to connect to the TFS via Visual Studio (this also works fine internally)
I'm having a hard time finding any documentation on how to acheive this.
I just installed VS2010 and opened the root machine.config and web.config files for review and I found some errors. In machine.config, the following line has errors in both entries for <Microsoft.VisualStudio.Diagnostics.ServiceModelSink.Behavior>. When I hover the cursor over them I get a tooltip text which displays: "The element 'endpointBehaviors' has invalid child element 'Microsoft.VisualStudio.Diagnostics.ServiceModelSink.Behavior'. List of possible elements expected: '...(list of options here)...'. The same problem happens for the second appereance in tag <serviceBehaviors>.
[Code]....
In web.config, there is a tag called <protocols> that has an error with a tooltip text that says "The element 'system.web' has invalid child element 'protocols'. List of possible elements expected: '...(list of options here)...'.
Right now, I'm doing it with an executable on the post-build event by looking at the assembly to get the version and stuff that into the web.config. It works, but isn't exactly what I was looking for.
I have an add-on for a commercial ASP.NET website. My add-on requires people to merge entries into their web.config, add/overwrite existing files, and add some DLL files to the bin folder. Is there a good and safe way to create an installer than can do this with a wizard type of installation?
I really like the new transformation feature for the web.config. It seems to work when I do "Build deployment package" but not when I just want to locally start the debugging using the green arrow. It just uses the web.config without processing theWeb.Debug.config. I can prove that because in web.config I have debug="false" with a transformation in Web.Debug.config so that it gets true but everytime VS asks if it should modify the web.config to enable debugging which it should've done automatically with the following transformation:
[Code]....
Am I missing something here? I used to work with NAnt to modify/create the web.config as a pre-build event but I thought that I wouldn't need it anymore. Am I wrong? The project is a freshly created asp.net mvc 2 web application.
I want to move the App.config file from MyClassLibrary1 project to the bin of the MyClassLibrary2. I want to do this on post build in VS or MSBuild using relative paths if possible. This way anybody checking out the projects will not have to modify any paths if they choose to locate the project in a different location.
I have already tried the following approaches but to no avail.
Today I started playing with the web.config transforms in VS 2010. To begin with, I attempted the same hello world example that features in a lot of the blog posts on this topic - updating a connection string.
I created the minimal example shown below (and similar to the one found in this blog). The problem is that whenever I do a right-click -> "Publish", or a right-click -> "Build Deployment Package" on the .csproj file, I'm not getting the correct output. Rather than a transformed web.config, I'm getting no web.config, and instead the two transform files are included.
I'm trying to develop my first web application using Web.Config transformations.Trying to run the app (building with the "Dev" build configuration)in the Asp.Net Debugging web server built into VS the site doesn't seem to work - the "Web.Dev.config" configuration doesn't appear to be seen by the application.
I'd like to add build configuration dependant web config files to my empty ASP.NET 4 Web site project. How can I do that? According to this blog entry, VS 2010 is supposed to provide a context menu entry on the original web.config file, Add Config Transform, allowing to add build configuration dependant web.config files to the project. But this context menu entry doesn't exist. What did I do wrong?
Steps to reproduce:
Create an empty ASP.NET 4 Web site project on localhost (IIS)
I had no problem with this in Visual Studio 2008 but it seems that VS 2010 is having an issue, and I'm betting it's probably me.I have a solution with an ASP.NET Web Site Project and a few C# projects (BLL, DAL, Tests in NUnit). I have configured the build process for the test project to automatically run NUnit to run the tests. I would like to ensure that the BLL and DAL projects build before the test project so that the tests will run against the latest compiled version (yes, I know I could do this all in one project, but I'm choosing not to -- please bear with me :) )
So, I set the dependencies of the Test project to include the BLL, DAL, and Web Application projects, and the build order shows BLL, DAL, Web Application, and then Tests. However, I noticed that the BLL doesn't actually build when I build the Test project.Any idea what this could be or any option I might be missing to force the other projects to build when I build the Test project?
Removing this and replacing it with a normal text, it will work. The way I setup the XML datasource:
xmlDataSource.TransformArgumentList.AddExtensionObject("ds:HttpUtility", new System.Web.HttpUtility()); xmlDataSource.Data = Cache.FetchPageMenu();
I've been searching the Microsoft pages for any changes in v4, but can't find any. All this worked fine in v3.5 (and before v2). Not receiving any errors, the data is just not displaying.
I'm a fan of the new VS 2010 Web.config transformations. I use this feature for deployment purposes and wondered if it is possible to use them for debugging too.I think of using them in the IDE: I want to create different built configuration (with linked transformation configurations); choose one of them; start the web site in the IDE and debug the different configurations this way.
I don't understand how to use this feature called "Build deployment package" in VS 2010. I go to my properties and go to package/publish web and setup it up. I click "Create deployment package as zip"
I then build the deployment package and get a zip file.
When I look into and start drilling down in the folders I find I get a path like this
[Code]....
I don't understand why it makes all these folders and on top of it why is it my path to where my soultion sits. I don't like the fact that now everyone can look in the zip and see my accoutn name, where the file was sitting, that I am using subversion.
Then it makes it so confusing to when a error happens. I deployed it on my IIS windows 2008 server and ran it and I had a error show up. It pointed to the file where the error occured and the path was point to my desktop.For the longest time I could not understand why it was pointing to my windows 7 machine desktop when it was running on a windows 2008 server located in a different country.
It was not until I found out with the zip path it made sense. But that is confusing when it is pointing to paths that don't exist on that computer.
