Skip to main content

70-562 Deployment

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.

Comments

Popular posts from this blog

Rxjs Forkjoin vs Zip

These Rxjs combination operators are handy to make Rest calls in parallel and combine their results. Both take n observables and will return the results, with the difference that forkJoin will complete even if one of the nested observables errors of completes.

React JS Patterns

React JS is always evolving, and evolving quickly. These evolutions can be very significant ones, for example, the addition of hooks. React has a lot of code patterns, often these patterns are motivated by the DRY and/or the open-close principle. These patterns sometimes come in to replace a previous one, yet the previous ones still stays in use, as a consequence, the list of patterns keep growing. The goal of the next few posts will be to list the patterns commonly used in React JS developpement. Some patterns are more specific to JSX and I will start with these, and maybe add patterns specific to Redux.

Javascript: Closure and Lexical Scope

The two are separate topics, I just happen to put them in the same post for now. Closure Closure is the capability to remember it's lexical scope, even when executed outside it's lexical scope. If two inner functions, are within the same scope, they share the same closure.     Lexical scope The lexical scope is the scope in which a variable is declared during the first pass of the javascript compilation, which has two passes, compilation and execution. During the compilation pass, the compiler goes through the code looking for formal declaration, that is, var, function and parameters of function. For each of these formal declarations, the compiler will check the current lexical scope, and add this identifier if it isn't already there. Then at the second pass, execution, the compiler will run the code as we are intuitively use to and once it reaches the the identifiers found earlier, will ask if they are left hand side(RHS), or right hand side (LHS). If th...