Thursday, May 4, PM. User posted Well, I suppose if I had taken the time to read the web page I would have known that. But hey, I'm a developer, we don't read documentation :. User posted hi have you shorted out your problem. Sunday, April 6, PM. Tuesday, June 10, PM. Thank you. Wednesday, July 30, AM. User posted hi I used ur technique.
It's perfectly working. I had searched lot but couldnt find ans like urs. Thanks Jitendra. Saturday, September 20, AM. User posted Now its working fine for me Saturday, September 20, PM. User posted Hi.. Tuesday, September 23, AM. User posted Hey Hi, Thanks this post worked for me. Tuesday, June 23, AM.
This will prompt me for what I want to name the project and where to store its project file:. The web deployment project will then show up as part of my solution:. Note that a single web-site project can optionally have multiple deployment projects associated with it.
You can also have multiple web-site projects in a solution, each with a separate web deployment project for example: a user control library project that you pre-compiled and then copied into another web app project that used it.
Step 3: Setting Build and Deployment Options. To customize build and deployment settings I can either use the built-in GUI property pages for the deployment project, or edit the MSBuild file directly. Here are a few of the more common things developers will want to control:. Only the later option was supported in VS — and meant that you always had to deploy your. NET at runtime the first time the app was run. NET 2. This produces a more efficient version of the app, and eliminates the need for a first-time dynamic compile performance hit when your app is run.
It also allows you to protect more of the IP of your site, and enables you better compile-time checking of your application.
The first property page in the web deployment project allows you to choose either this new compile mode, or the preserve. The default option is to merge the entire web-site into a single assembly that you can name however you want. There are other options you can choose as well for more granular control over the assembly generation. For example, the second option above lets you compile each folder in your website into a separate named assembly for example: MyCompany.
Folder1, MyCompany. This is useful for patching large applications where you want to make a tactical update to just a portion of the site. If you have an AssemblyInfo.
Alternatively, you can also set the version information specifically in the IDE. This in turn saves it as an MSBuild variable in your project file. You could optionally use a custom MSbuild task to set this variable dynamically at build-time for example: to use a policy like we do at Microsoft where the build number is based on the current date.
This can be done on a configuration section by section basis. Simply list the name of the section to replace, and an XML file containing the replacement settings. You can choose to have them replaced either in-line within the web. The above GUI property pages provide support for the most common build configuration settings. One neat thing about the Web Deployment Projects, though, is that there is easy IDE support for dropping down into the MSBuild file directly and customizing things further.
This will bring up an XML editor with intellisense support for the project file:. You can make changes, and then hit save to update things dynamically. The web deployment project adds support for pre and post build events that you can use to customize things. MSBuild itself ships with tons and tons of built-in build tasks like MakeDir.
The really cool thing is that it is also easy to build your own MSBuild tasks and add them to projects as well. Note that you can still use the property page dialogs above even after customizing the project file — it will preserve your settings and not blow them away. Step 5: Building the Web Deployment Project. This will then generate an output folder for my website.
The web. You can easily configure this in the VS build configuration manager:. You can then use the build configuration drop-down on the toolbar to quickly switch between debug and release modes depending on where you are with the project:.
Step 6: Optional Setup Project. This is a standard VS project type that supports packaging a. MSI setup program for my web application that will walk me through creating an IIS vroot and deploy my production app on a web-server when run:. Next Steps. We'll then gather and incorporate feedback and release an updated version later this year. We hope you find it useful. But there is one thing I really don't understand..
When we create an asp. As if I need an database there? And when I use the current deployment tool, it tries to do something with the database file, which of course is locked by sql server.. Will these things also be fixed with this? Hi Steven, It should be on the web later this week.
I'll post a new entry with a link to the download as soon as it is out. Thanks, Scott. Scott, One of the things I miss with the standard VS setup is being able to call static methods on a page from another page within the project. This is no longer possible due to each page being compiled into its own assembly. However, this download will provide the option to deploy a web site as a single assembly as VS used to do. Will this tool change the development-time experience too.
For example will I be able to reference one page from another maybe even have Intellisense for this? Looks great, but is there any equivalent in vs to use until we have upgraded to. Scott, Can't wait to get this tool! Thank you for the heads up and explanation on what and how etc. Hi Scott, Sounds intersting, but i gatta one questions, what are the pitfalls on this approach i mean disadvantages or can you please tell me the Best Practice for this approach Do's and Don'ts?
Thanks, Smith. Does this mean I have to have my website in a solution to see that build option? Hi Lee, The above utility doesn't change the development time experience where multiple assemblies are created to enable quicker updates -- instead it uses a post-build step that merges these assemblies into one. So it won't change the existing semantics you see in your code.
You can still use static or instance methods across pages or controls in VS You can then call static methods on it. Hope this helps, Scott. I like the idea of building assemblies for seperate directories, I know it will make life much easier for large websites. Will the update of certain assemblies on certain directories kill the application state? And if so, would it be easier to let IIS compile the pages on demand? How does this compare to the Team Build server as part of Team System?
Can this integrate into that? Or are they completely 2 different procedures? Thanks for another gread add-on to an already terrific product. I'd love to see an option in the web setup project where the user who is running setup. Maybe, this developers are accustomed with ASP.
NET 1. So unfortunately this would cause the loss of application state. Hi Scott Lee, The above solution ends up generating a MSbuild based project file that can be easily integrated into Team Build or any other command-line or automated build process you might have.
So you can use it either in the IDE as I've shown above , or on the command-line or Team Build environments which makes it a pretty sweet solution. Hi Israel, Yep -- some people want a single dll. That is why we made it the default option with the Web Deployment Projects even though I personally think multiple DLLs are more flexible as long as they are named consistently and can be easily updated. One thing to call out is that when using the web deployment project we first build the web-site into several DLLs, and then as a post-build step merge them into the final assemblies we are using ILMerge functionality to-do this -- which means you can do cool things like merge a VB and C assembly together.
This does mean that you get the same compilation semantics in terms of referencing types that you get today with the web-site projects in VS the programming model is identical. Of course, this is a much more comprehensive solution! Thanks for getting this done so quickly. Cheers, Robert. Hi Robert, Glad it looks good! If you'd prefer to use nant or another build environment vs. I don't prefer nant -- I just preferred it to VS's build support.
Now we're pushing hard on a full release of our stuff all. BTW: I blogged on this port over the last month, if you are interested, check it out. Thanks again, Robert. Hi Scott Lee, Team Build does integrate with this cool add in. You can find the integration details soon on my blog as a follow up to the web deployment project post.
This is great - its exactly what I've been trying to do. A couple of problems though; I want to replace the web. Is it possible to specify an XPath or similar to replace a sub node of the web.
As I can't currently do the above, I've changed it to replace the entire system. Looks like it will be perfect when I cant get these problems resolved!
Thanks Adam. Hey Scott, Cool!!! Thank you very much for this information. Firoz Ansari. Hi Scott, Tnx for all the effort you guys put in and especially for the information you put online here, really helpfull ;- I still have one issue that we are struggling with here at our company, till now we had the following development architecture: One single development server for all projects, which has a setup that is exactly the same as the Staging and Live server.
On this we have a share, each developer has one with for there own, in which the webproject is put. Using that we can develop and build using the filesystem Access but debug using the remote IIS. I cannot seem to get this scenario working with VS For us it is quite important, as a quality assurance, that the developers are working on the remote IIS Development Server.
This also allows us to test the whole security architecture we have implemented during the development. I hope you can give me a hint here. Thanks, Martijn. Hi Adam, Can you send me an email scottgu microsoft. I want to understand better why the merge failed for your app. We can then debug and try and figure out what the issue is.
Is add-in work or planned to work in WebDev Express? Sorry about that, Scott. Maybe I'm missing it but I still don't see the ability to put my own namespace hierarchy on control libraries, even with this add-on tool. I need to be able to develop a user control library as a single DLL with my company's namespacing conventions on all the controls.
I certainly don't want each control to be in the generic ASP. Is this supported? Was wondering how all this helps me find out what configuration I am using from code? I would like to still be able to do this.
The [Conditional] attribute does not seem to help as it only seems to apply to classes and class members. Am I missing something? Can't get project references in. What I want is to build. Cheers Ben. Hi Scott, Thanks for this tool, its a great addition! I'm setting up a test project right now for dev, stage and release builds. I have app and connection string replacement config files setup for each build type. When I run any one of the builds, all app and connection string config files are moved to the target directory.
Near the end of the build, the app and connnection string config files for the current build are deleted. I then get an error in vs stating that it can't find the relevant config files. Seems like the reverse should happen, i. Any ideas? Thanks, Chris. Hi Scott, I just sent in a message re all the config files being moved to the target dir during the build, and the config files matching the build type being deleted.
Here's an update: I think this behavior was caused by my taking a short cut, namely giving both the appSettings and connectionStrings variables the same file name to merge. When I removed this, a separate file for each variable the behavior ceased. I've since moved all the build specfic config files into their own dir, and excluded it from the deploy list and all is working as it should, i. Hi Ben, Usually an error like that is caused by having a duplicate class name in your project.
Then check the output window after your next build and you'll see what the problem is. Hey Scott. The wdproj has a reference to the project which generates the assembly. What needs to be done to make the build process find my assembly? Derek Greer dgreer fedex. Hi scott My references come from other projects in solution, but I can't build. I need to build. I looked through Microsoft. HI Scott Please clarify this issue. My question is..
Note that there will also be a few. NET to reference and find the appropriate classes for your pages -- but all of your. Okay here is a good question then, I have implemented the Web Deployment Add-In and I have set not to include debug information but when I compile I still have pdb files in my bin folder from all other referenced projects??
They are all set to release mode as well. How can I stop the produciton of the debug database files when creating a release build. And one other thing.. Anyone any ideas on this please as I am now going round in circles. Many Thanks Greg. I tried to deploy couple of my projects just converted to VS My pages are windows encoded. In PrecompiledWeb folder everything looks good, but in deployment folder all cyrillic characters are gone.
Is there any way to help it without converting all the pages to Unicode? Also, it would be nice to be able to perform parameter replacements on custom config files other than web. Hi Greg, By default when you build in a release configuration, VS generated PDB debug info along with your assemblies the idea being that you can then optionally choose to deploy those or not as a post-build step.
I have same problem as Humpy. This tool is using following construct ion in method BuilderManager. GetConfig configPath. Sorry for my bad english Hi Martin, I developer on the team just saw your post on the asp. We are also then looking to fix it in the next download of the web deployment project.
Scott, thanks for the quick response and help! You are the masters! This is exactly what I have been waiting for! I'm having trouble figuring out how to update custom sections in Web. Web and fails. Any clues as to how to replace sections in web.
Thanks, Eric. Hi Eric, Any chance you could send me email scottgu microsoft. I can then loop a few people in who might be able to help. Frontpage has it. Why not VS? It seems to me there is no technical reason why this couldn't be done. The deployment parameters should be specified once and then upon a single click of an icon just the changes should be propagated to the live site.
This is obviously the optimal way to deploy a site. Or is this possible now and I'm missing something? The error does not say much; however, I did find out that it was a duplicate class. OK, with padi. So the following is a quick way to isolate the problem and fin the duplicate s. Regards, Simon Morgan. Hi Scott thanks for that. So then I take it there is no one-click deploy for standard VS web applications? Hi Forsooth, If you have a standard Web Site project, you can choose the "Publish Web" option from the build menu to build and publish a site remotely.
It doesn't have all of the features that web deployment projects provide -- but does provide basic 1 click deployment. In the next release we are planning to add signficantly more features to this area as well. The project compiles fine, but when i go to build it with the deployment project it throws this error. Basically, my end goal is to have my core web application that has master pages. Any help would be appreciated, Gabe gkeller r-effects. You should be able to use these to figure out what is going on.
Hi Scott, The Web Deployment Project is an excellent effort to ease the deployment of the web projects. Thankyou all for this greate add-in. I have problem similar to the one presented by Eric Schoen on 26th May, My application has its own custom sectionGroup and its own sections.
I want to replace the entire sectionGroup during the Deployment or i can even perform replacement of the individual sections. But when i start defining the replacements in the property pages, i keep getting the error : web. If Eric has sent you an email as requested by you, then it would really help me if you can give me the solution for this scenario.
I can send you the config file if you want for further analysis. Thanks, Saleem. Hi Saleem, Can you send me an email scottgu microsoft. I can then loop you in with a person here who can help. Hi MedCon, Can you send me an email scottgu microsoft.
I can then get someone on the team to help. Net 1. Essentially, I want a one-button incremental deployment option. Hi, The Web Deployment Project tool has two different release dates. One is around Nov , and another one is April 4th What's the difference? How can I remove the eariler one in order to install the later version?
Hi Natalie, The November release was the first version. We have since released a newer version that has a number of bug-fixes and a few features. To install the new version, just uninstall the old one, and then run the new version's installer. Hi Scott, How can I exclude from a build the files that are not required for an application to run? Improve this answer. Simply replacing that tag with these other GUIDs, you can reload the project and it should open as expected without any major implications.
I think I already installed SP1, dunno if that is needed. I installed WebApplicationProjectSetup. The following two patches fixed this for me install in this order. Cristian Diaconescu Cristian Diaconescu JaredPar JaredPar k gold badges silver badges bronze badges. Sign up or log in Sign up using Google. Sign up using Facebook.
Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Podcast Making Agile work for data science. Stack Gives Back Featured on Meta.
0コメント