shahab Posted March 9, 2004 Posted March 9, 2004 Dear friends, You know that every change in ASP.NET Project needs a new compiling for updating dll files in bin directory. However, sometimes the programmer needs to change a name of a hyperlink or gif or some of very small details� Should the programmer compile hundred pages (for a hard code web site) only because of small updates? What are the limitations in this field? is there any chance to preventing a new compile?) :) :p Quote
*Gurus* Derek Stone Posted March 9, 2004 *Gurus* Posted March 9, 2004 No. If your project was properly structured (n-tier), you wouldn't have to recompile all of it to make simple changes such as those. Quote Posting Guidelines
Moderators Robby Posted March 9, 2004 Moderators Posted March 9, 2004 Also, if the changes are only to the aspx file and don't involve renaming of controls or new controls that require server-side handling then simply saving the changes will do. (There is no need to recompile) Also, if you have multiple porjects you can exclude some from the recompile list in the solution properties. Quote Visit...Bassic Software
samsmithnz Posted March 9, 2004 Posted March 9, 2004 Also, you'd do better to have all your URL's out of the server side code, if you really need them in there, they should be referenced in the web.config, so that a url change doesn't require a new compile. Quote Thanks Sam http://www.samsmith.co.nz
shahab Posted March 9, 2004 Author Posted March 9, 2004 If your project was properly structured (n-tier) I am not familiar enough ;) with the aspects of this architecture(n-tier)! Would u please explain about those aspects or introduce an article. ************************************************* they should be referenced in the web.config, so that a url change doesn't require a new compile. Would u please show me a code of that? :) thanks Quote
samsmithnz Posted March 9, 2004 Posted March 9, 2004 N-tiered jsut means that you have layers (usually 3), user interface, business objects/rules and the database and/or objects. The idea is that if its coded correctly, that any one layer can be pulled out and replaced with a different layer and the app will still work. Some examples: 1. Replace Oracle with SQL Server 2. Replace a Windows interface with a ASP.NET web interface 3. Replace some VB6 business objects with some VB.NET ones There are plenty of examples on the web. as for web.config. <appSettings> <!--ConnectionString--> <add key="ConnectionString" value="server=DEV;database=mydb;uid=db_sys;pwd=" /> </appSettings> Then add a line simliar to this to read it: ConfigurationSettings.AppSettings.Get("ConnectionString") Quote Thanks Sam http://www.samsmith.co.nz
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.