Tuesday, March 31, 2009
There are physical differences, compilation differences, and they are for different usage scenarios.
First of all, what's the difference btw a website and a web application?
For one, a web application is on a modular scaffold of logically connected namespaces. It uses a central codebase and can be added to at any time, from a variety of directories. A web site conversely is locked down by file structure, so to speak.
So if you are a codewolf, why would you ever go with a Web Site instead of a Web Application?
There are fundamental and deep differences between the two.
Known as the "2005" web project model
Uses a folder-based approach to web dev
Typically associated with moving 2003 projects to 2008
Known as the "2003" web project model
Uses a project-based approach to web development
Created to address some of the feedback from customers
In short, the 2003 model was project-based, which was great for .NET but not platform agnostic for other deployment environs such as dreamweaver. Those type of platforms are folder-driven and don't read code to establish connections.
Web applications are packaged into dlls, while web sites are not.
Notice some immediate diffs btw web sites and web applications:
Websites use a folder-based style, so it matters which folder you put your content in.
Websites do not run on VisualStudio, they run on IIS.
Websites have a solution file (file that launches the solution), but all it does is launch the solution into VS2008.
More at http://blogs.msdn.com/zainnab/
Thursday, March 26, 2009
To deploy WebORB into an existing ASP.NET application, follow the steps below:
1. Copy the following files/folders from the default Weborb installation directory to the corresponding folders in the target virtual directory:
/weborb.js (required only for the AJAX clients)
2. Add the following XML configuration to web.config in the target virtual directory:
(Thanks to formatmysourcecode.blogspot.com for code formatting)
<add verb="*" path="weborb.aspx" type="Weborb.ORBHttpHandler"/>
<add verb="*" path="codegen.aspx" type= "Weborb.Management.CodeGen.CodegeneratorHttpHandler"/>
3. (Optional) To deploy console, example and code generator, copy the following folders with all files and subdirectories:
/all mdb files from the root
4. (Optional) Create /logs folder as the place where WebORB stores its log files
5. Grant Write permission to the user account ASP.NET uses for the following files and directories:
/weborb.config (required only if making configuration changes from the console)
/logs (required only if logging is enabled)
/weborbassets/codegen (required only if codegen is used in the console)
/*.mdb (required only if writing data back on the server in some examples)
Additional steps may be required to configure logging and code generation features when deploying WebORB into another application. Generally the user account used by ASP.NET needs to have Write permission to the following files and folders:
Please direct any questions or comments to http://groups.yahoo.com/group/flashorb/.
Tuesday, March 10, 2009
Microsoft Management Console
- Start local IIS
- Start local SQL Server
- Create new ASP.NET site of type .NET Web Application
- Install Forms Authentication Framework to establish user accounts
- Add provision for Web.sitemap
- Create Web.sitemap
- Add siteMap entry to web.config
- User Authentication
- Install Forms Authentication schema to application
- Customize FormsAuthentication class for user accounts