Web Development and Deployment with Visual Studio 2010

Posted By: Jason Olson | Nov 14th, 2008 @ 8:29 AM | 79,060 Views | 11 Comments

Formats:

Screencast

Welcome back to another Visual Studio 2010 and .NET Framework 4.0 Week video. In this latest installment, we catch up with Vishal Joshi, Senior Program Manager on the Web Development Tools team.

In this video, Vishal shows us what is being done in Visual Studio 2010 around web development and deployment. Covered are topics like JQuery support, HTML code snippets, better Intellisense, and a whole slew of new features around web deployment.

Enjoy!

This is another Visual Studio 2010 and .NET Framework 4.0 Week Video. For other Visual Studio 2010 videos, check out the Visual Studio topic area here on Channel 9.

Tag: Visual Studio

Rating:

Luda

Thanks for the video. I'm looking forward to the deployment packaging feature. Can it be configured per destination environment: Stage (QA), User Acceptance (Client), Production (Live)? These environments are not identical. Is the new web.config (debug vs. release) the way to address different destination environments?

Aside: As a security precaution, do not show people on video typing in their password. If I am determined enough, I might be able to guess vijoshi's password at video time mark: 20.35. You might want to edit that part out and vijoshi change his password.

VISHRAJK149
VishalRJoshi

You can go to Build-->Configuration and add all different destination configurations like Staging, UAT, Production etc... Next when you right click on your web.config file you will be able to see a command "Add Config Transforms"... This command will add web.staging.config, web.UAT.config, web.production.config to your project... Hope this helps...
Thanks much for the security hint... I have changed my password now... Smiley
Vishal R. Joshi | http://vishaljoshi.blogspot.com

Ashish Chettiar
Coding --- My Passion

All of the stuff is great.
Now i guess MS will start working on integrating the query analyzer in VS and provide debug functionality for it.
Coz as a VS developer i have faced many difficulties in finding the bugs in stored proc's which r like 1700 lines long or so.
If that happens then there will be no stopping VS.

if u guys r not working on that then maybe u can take a que. Smiley

Regards,
Ashish S Chettiar.

Naresh Gupta

Thanks Vishal for sharing web deployment enhancements in VS 2010. I do have following questions, there may be a way already which is not shown in the video:

How to deploy SharePoint webpart using this feature?
I would like to add/replace/update the section of web.config at production server like SafeControls, namespaces, public token, version number etc. If I understood correctly from demo that package will always replace the web.config. Is my understanding correct? web.config at production server(s) may have webparts deployed by other department developers within the agency.
How do you handle such scenarios as desribed in #2?
How to use deployment feature to deploy site in the farm environment?
Is there a way to specify the dynamic destination server name? not a hard coded destination as shown in the demo. It would be nice at deployment, system administrator will be presented with a choice of single server name or farm.

Looking forward to hear from you soon.

Regards,

Naresh Gupta

VISHRAJK149
VishalRJoshi

Hi Naresh,
Plz find the responses to your questions inline...

How to deploy SharePoint webpart using this feature? --> Vishal: Currently sharepoint webparts are not part of this deployment story but there is a solution for that too, please check out the video http://channel9.msdn.com/posts/VisualStudio/Sharepoint-Development-with-Visual-Studio-2010/
I would like to add/replace/update the section of web.config at production server like SafeControls, namespaces, public token, version number etc. If I understood correctly from demo that package will always replace the web.config. Is my understanding correct? web.config at production server(s) may have webparts deployed by other department developers within the agency. --> Vishal: You bring out a good point, currently the web.config file is replaced on the server which means that changes by other departments will be lost... MSDeploy which is the underlying technology for web deployment is provider based model, it has providers for GAC, COM, IIS Settings, Registry, Web Content and so on... There will be an opportunity eventually where you can write a simple provider which takes the new web.config produced by VS10 and merge it on the server...
How do you handle such scenarios as desribed in #2? --> Vishal: As mentioned above
How to use deployment feature to deploy site in the farm environment? --> Vishal: The web package which is produced by VS10 can then be applied to every server in the web farm by using MSDeploy command line directly... That step is manual today but we will be considering an automatic solution for that in the future...
Is there a way to specify the dynamic destination server name? not a hard coded destination as shown in the demo. It would be nice at deployment, system administrator will be presented with a choice of single server name or farm. --> Vishal: Yes that is feasible... That concept is called parameterization within MSDeploy; where you can mark certain items as parameters... The steps to do this would be, create a package using VS10, deploy it to your staging server with fixed destination names... Use InetMgr to take this newly deployed site, parameterize your config file with mandatory parameters like server name and when the package is installed (again using InetMgr or commandline) your system administrator can provide the values at install time. This is explained in the PDC session http://channel9.msdn.com/pdc2008/ES15/

If you like more details on all these functionalities you can also view the PDC session http://channel9.msdn.com/pdc2008/PC33/ in which I go into much more details...

wishes
Vishal | http://vishaljoshi.blogspot.com

Naresh Gupta

Thanks Vishal. I hope such tools may be available as add-on to Visual Studio 2008.

ddurose

In reply to VISHRAJK149

#Nov 15th, 2008 @ 1:08 AM

It's about time that Visual Studio had a decent "Publish" feature inside it. Having the ability to save different deployment scenarios (i.e. pushing code to staging, pushing code to production, etc.) seems like such a basic feature that should have been present years ago. Anyways, I'm glad it's going to be easier in VS2010. Having to manually go into my web.config and change around connection strings every time I want to publish to dev or prod is such a pain. I have been getting around it by running a script inside a tool called Nant-GUI. I guess I'll have to wait and see whether having the web.debug.config and a web.release.config with the xml transforms will make the overall deployment process easier. I'm skeptical, but hopeful. =) Will there be a GUI to perform these xml transforms?

VISHRAJK149
VishalRJoshi

In reply to ddurose

#Jan 16th @ 12:29 PM

ddurose,
I am optimistic that your wait will be worth it... There will not be a GUI to perform these xml transforms but believe me the syntax is very very simple... I am soon hoping to write a blog post explaining it so if you like please keep reading my blogposts on the all the improvements on the space http://vishaljoshi.blogspot.com/
Also do not hesitate to write me an email at vishal.joshi@microsoft.com in case you have any feedback/comment...
wishes
Vishal

simyaci
SiMYACI

yaw a.q download yokmu