Now deploy to file system on local hardrive. Open resulting web.config and see <value> setting has extrac carriag return and bunch of tabs in front of it..
I want to use the web.config transformation that works fine for publish also for debugging.When i publish a web app, visual studio automatically transforms the web.config based on my currenc build configuration.How can i tell visual studio to do the same when i start debugging.On debug start it simply uses the default web.config without transformation.
I have installed VS2010 ultimate and have read with interest about the new publish options, config transformations but none of them are available. I have tried creating different release versions and cannot see the option, also have no new options for publish, just look like the VS2008 ones.
Is there some service pack or pack that i need to install these or does it sound like a reinstall?
I just recently upgrade my asp.net web project from visual studio 2005 to visual studio 2010. The upgrade was successful with no problems however im missing some features with this project. The One Click Publish feature(which is greyed out) in the header area of Visual Studio 2010 and the Add Config Transforms feature which is no where to be seen when you right click on web.config. When i create a new web project straight from visual studio 2010, these options work fine.
I made a custom server control library that all of our websites will be using. I have registered the dll in the global web.config of our production and development servers, and everything runs fine in the browser. The only problem I have is Visual Studio/Intellisense not recognizing my control. I get the error message "Unknown server tag...", which in turn throws other validation warnings. Does anyone know how to tell Visual Studio to include dll's registered in this location? Our sites are .net 4.0 and below is an excerpt from the web.config located in %SystemDrive%WindowsMicrosoft.NETFrameworkv4.0.30319Config on the servers.
when i opened my Visual Studio 2010 i noticed that my ajax tab was missing from my toolbox and ajax control kit too.Then i noticed even that when i create new website, there is no web.config in it and it should be.WHAT IS GOIN ON???? :/
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)...'.
We deployed version 2.0 to our client. But we converted from .Net 2.0 to .NET 3.5 in our development area. When we are deploying the modified module to our client, We are getting error because the client site is referring 2.0. We told the client to upgrade the .NET framework to 3.5. Though they are upgrading to 3.5, the web.config will refer to 2.0 only. We can't open the project in vs 2010 in the client place. Client system does not have project file. How can I convert the web.config?
I have switched over from VS2008 to VS10 (.Net4) and I program in Silverlight. But this problem isn't related to the Silverlight but more so to ASP.Net and that's why I bring it up here. My problem is if I create a SL or even a plain ASP.Net Web app, and I go to Project|ASP Configuration and click on security I get error that it can't find the database. After lots of testing, it turns out if there is no connection string with the name "LocalSqlServe" in my web.config, it does not find Machine.Config in the .Net Framework to get it's default. It also happens at runtime and not just in VS. So, my machine ASP.Net can't find machine.config file. I'm running Vista 32.
When I want to build my website it complains the web.debug.config file cannot be copied.I can't find this file, how can I restore it?I do have a web.config file!
In the Setup Project I have 2 web.config files: web.config - used during the development and web_dist.config - the one that should be included into Setup Project. I must be sure the the Setup project will NOT include the web.config and will always include web_dist.config.
In the File System -> Web Application Folder I have added the Content Files from the project. Also included the web_dist.config and mapped it to the web.config.
But this gives the warning:
WARNING: Two or more objects have the same target location ('[targetdir]web.config') And the actual config file included is web.config and not web_dist.config. What would be the best option to include the web_dist.config (and named as web.config in the setup)?
I just moved into a new computer running Windows 7 pro, and I installed a new copy of VS2010. Now all of my old sites that I made in VS2008 do not have their web.config files. Does anyone know what happens to them in VS2010, or Windows 7?
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'm using VS 2010 Express Edition (VWD) to develop a website project that will be deployed to a Windows 2000 Server (targeting .NET 2.0). BACKGROUND: The website was new, so I chose the 'c# blank website' project template in VS 2010. This (as you may know) gave me an extremely more lean web.config file than VS 2008. I like that for 4.0 development, but I'm going to be deploying it to the testing region tomorrow and I'm getting concerned that all that extra stuff that used to be in the web.config is going to bite me.
I work in an development group in an enterprise, where we strive to seperate business units and their responsibilities. So for example, I am in the development group and we are responsible for all tasks related to developing applications. We have other roles such as dbas, or operational roles that are outside of our group and are responsible for things like deployment, server maintenance, etc.
I'm looking at features in VS such as the publish web app feature and the web.config transform feature and reading about them in blogs and various other places. Based on the majority of what I read it always seems that the writer is assuming that the developer is managing things like connection strings, user names, passwords for the different environments in web config transforms, then publishing to a remove server in some kind of production environment (be it live, or test or staging, etc).
An example is here. In our environment, and I assume others too, the scenario is somewhat more complex than is usually portrayed. The development group may not know where any of what they've developed is deployed. And administrators may move servers,databases etc and update configuration as characteristics of the environment dictate. So in these cases, how does web.config transforms help? Publish can still potentially be used locally to build artifacts for a deployment package but even you'd probably want to use some automated build manager instead.
So is publish and transforms really more suited for more rudimentary development processes where the barrier between development and operations is very grey? Or am I missing something? It just seems that a lot of things I've reading about this kind of thing have good intentions but are somewhat superficial in the context of a more defined development process.
Interested to know others opinions and experiences on this.
Does anyone no why web.config transforms are not available for Web Site Projects in VS2010. I thought that Web Site Projects where once introduced as the successor of Web Application Projects. But now the lack the deployment feature which I would really like to use.
Maybe someone knows a workaround, without having to convert 70 websites? Converting to Web Application Projects isn't a real option because I use Table Profile Provider by Hao Kong, which doesn't work with this type of project.
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.
My web site used ASP.NET 3.5 SP1, MVC 2, and EF. Last night I tried to upgrade to ASP.NET 4 (& EF4) under VS2010.
If my views are compiled (MvcBuildViews property is true), then the build fails with this error message: Error 5 Could not load type 'System.Data.Entity.Design.AspNet.EntityDesignerBuildProvider'. C:WindowsMicrosoft.NETFrameworkv4.0.30319Configweb.config 129
It's actually complaining about my system web.config file.
If MvcBuildViews is false, then it will run (and compile the views normally just fine).
OS: Server 2008 R2, all updates applied at time of writing.
A while ago when i started using VS 2005, i found that some assembly entries were automatically added to from web.config
and i was getting annoying errors. later i found i have added unneccessary references in my application. And its a feature that assembly reference are automatically added to assembly tag in Web.config, So dev don't have to worry about it.
Recently i used Interop.OWC11.dll in my application. And ^&*# got the annoying
"CS0234: The type or namespace name 'Office' does not exist in the namespace 'Microsoft' (are you missing an assembly reference?)"
error again.. Assembly entry was not added automatically. I checked same for existing references in my application, for them to automatic entries is not happening.... ? :(
I have to write is down in Web.config manually... I don't understand why?....
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?
