Deployment features in VS2008
Often a current version of visual studio will get new features with service packs and will later be included in the next release of visual studio, for example ajax in 2005 and deployment features.
Copy Web site: http or ftp
Publish web site: strong naming
The web deploymenbt project allows to manage the build aslo, on top of the setup program, all this is contaikned into an msbuild file(xml) witht he wdprof file extension.
It is possible to decide to include pdb or not, and manage output assemblies, for example, to remap which file will be put in which assembly.
Strong name signing is possible, and this requires a key file.
There is a configuration packager that allows to replace sections of the web.config file with replacement files, that need to go within the website directory.
You can tell it to remove the App_Data folder if you dont use it. Sections can be added to run after build.
Note on AJAX navigation history.
States are not saved to go to the previous state, and browser history works only with URLs. History feature has to be added manualy, in the script manager EnableHistory.
The ScriptManager's IsInAsyncPostBack and IsNavigating properties are usefull to check if in a ajax postback or navigating.
It will modify the query string of the url so that the 'back' button can be used, it can be incripted by setting the value in the web.config.
AJAX history makes it easier for the users to return to previous versions of the same page.
Often a current version of visual studio will get new features with service packs and will later be included in the next release of visual studio, for example ajax in 2005 and deployment features.
Copy Web site: http or ftp
Publish web site: strong naming
The web deploymenbt project allows to manage the build aslo, on top of the setup program, all this is contaikned into an msbuild file(xml) witht he wdprof file extension.
It is possible to decide to include pdb or not, and manage output assemblies, for example, to remap which file will be put in which assembly.
Strong name signing is possible, and this requires a key file.
There is a configuration packager that allows to replace sections of the web.config file with replacement files, that need to go within the website directory.
You can tell it to remove the App_Data folder if you dont use it. Sections can be added to run after build.
Note on AJAX navigation history.
States are not saved to go to the previous state, and browser history works only with URLs. History feature has to be added manualy, in the script manager EnableHistory.
The ScriptManager's IsInAsyncPostBack and IsNavigating properties are usefull to check if in a ajax postback or navigating.
It will modify the query string of the url so that the 'back' button can be used, it can be incripted by setting the value in the web.config.
AJAX history makes it easier for the users to return to previous versions of the same page.
Comments
Post a Comment