MTA Web Development Fundamentals Online Expert Session 2

  1. Machine.comfig
    • First file processed
    • %sysroot%\Microsoft.NET\framwork\<Ver Number>\CONFIG\
  2. web.config
    • Second file to be read
    • Stores the default settings for the web application.
    • %sysroot%\Microsoft.NET\framwork\<Ver Number>\CONFIG 
  3. web site, web.config file
    • <wwwroot>\web.comfig
    • best place to store application specific setting.
    • Can be created for subfolders, to appliy setting to a spicific folder
  4. application settings
    • Useful for static data like connection stringe (defines how to connect to a database)
    • Allows changes to be made esier. 
    • Allows other to make changes without you.
    • Can be modified: Manually, Programmatically, for visual studio project properties, Can use WSAT (web site administration tool) to edit in browser, and IIS has a configuration tool. 
  5. configSource
    Can be use to create a file that will deligate access to a site for a listed administrator to change only specified setting
  6. Error Pages
    • Reveals the cause of the error
    • Can help user get to where they are tyiing to go.
    • Never let the public see detailed error informaiton. can expose security vulnerabilites
  7. customeErrors
    • Element
    • can have sub elements
    • have RemoteOnly attibute which allows only the user to see error messages. Lets you troubleshoot error pages.
  8. Exceptions
    • Interrupt program flow
    • Catch most spicific type of eception possible
    • Best place to catch exception is a try-catch-finally block
    • Catch at page level with Page_Error or Page.ErrorPage
    • Can catch at the application level with web.config or Application_Error event
  9. try-catch-finally
    • try = code that might raise exception
    • catch = exception handler
    • finally = dispose of any items created by the block
  10. NotImplementedException
    Show that you intended to write code and forgot. 
  11. Application Deployment methods
    • Web Pacakages (New feature of Visual Studio 2010) takes entire application and compiles it into a zip file. Provides a command line file to automate install and supports configuring the web server.
    • Xcopy - Means using a command line tool to copy files. 
    • Publishing - publishing software contacts web server and uses web deploy to copy files and configure server. 
    • Windows Installer Package - ususally have a .msi or .exe extension. Easy for enterprise deployment. 
  12. Deployment Options
    • Precompiled - web applications are precomplied, wed-sites are not. 
    • Prevent Changes - for integrity. asp,net complitaion tool, MSBuild option, Web Deployment project
    • Single assembly - Makes the entire site a single DLL file. no one can see the source code. Create using Aspnet_Merge.exe after compiled, or use web deployment project.
  13. Application pool
    • Was introduced in windows server 2003. 
    • Protects application from each other by creating smaller Environment for them to run in. 
    • Usefull for using different versions of the .NET Framework
    • took our coping application pools at template in 2008 and 2008R2
  14. Discribe the horror that was a web server before Application Pools
    IIS 5, windows server 2000. Applications ran with the same the same privilefes as the wev server. Caused problems with application hogging all the rosources and crashing.
  15. cookies (client side)
    • little file stored clients side
    • sendts it back and forth to the server with ervery request.
    • last a long time
    • Session use cookies
    • can set the time out to anything
  16. query string (client side)
    • included in the URL
    • http://server/path/program?name=value
    • good for sharing
  17. view state (client side)
    • embeds hiddden data in the web page it's self
    • can grow big
    • allow web forms to work in web farms
    • can add data to view state
    • Encrypted and considered very secure
    • Only works if they click buttons not refresh, that will start over
  18. Session state(server side)
    • ASP spicific
    • spicific to user
    • uses encryption token to identify (cryptographically significant)
    • defaults to last 20 Mins
    • can be stored in memory, state server (useful in web farm), and databases.
  19. Appication (server side)
    • not user spicific
    • access by every user
    • works fast, stays in memory
  20. Database
    • Scaling - can store little or lots can be big or small
    • Centralized - Can access from multipule web servers
    • Reliable
Card Set
MTA Web Development Fundamentals Online Expert Session 2
These are my notes from the Online Expert MTA Web Development Fundamentals Session 2