Denver, CO, July 06, 2011 --(PR.com
)-- The advent of ASP.NET has made a whole new world open up. Over the last ten years programmers – particularly “old school” programmers – can now look at the World Wide Web not in design terms, as they used to when the Internet first went public, but in terms of developing an application. Thus, the term “web application” has come into being.
The particular advantage of ASP.NET is the clear and definitive separation of presentation and code. Developers who used Delphi, Visual Basic and other visual languages for applications development can appreciate this. A form is a form and is never confused with the code that affects the form’s behavior. Perhaps this was because the form was developed “visually” – one painted a form and it would be inconceivable to confuse this in any way, shape or form, with the code.
Some programmers remember the early days of Windows development when forms were created with code. But then there was the transformation of thinking that separated the layers. A similar thing seems to have happened with web development with ASP.NET – the code lies apart from the presentation layer or form. Classic ASP and Php not withstanding – a good programmer using these platforms should still ensure that code and presentation are separate (yes, it’s possible – it’s rarely done and most programmers confuse the two, but this is generally considered to be bad practice).
1 – Code reusability. In any environment, when one develops a site, it’s necessary to make a copy of any .js files. This means that when programmers develop sites and make changes to your script then, unless there is a central script repository, diverging copies result. This is generally considered to be a bad thing. Even if there is a script repository then any changes must be copied back. If not then the result will also be diverging copies.
In Visual Studio it is possible to create class libraries for server side code and this can be one library that is shared amongst several sites, but when a .js file is imported, Visual Studio makes a copy of the file.
3 – Overhead. With Internet download speeds getting faster this may not seem like as much of a problem as it did when programmers used limited memory machines on slow phone line connections but why have all of that dross when only a fraction is needed? Abundance is still no reason for waste. No one would carry their entire chest of drawers on a plane for an overnight trip when only one pair of underwear, socks and a shirt is needed.
The programmers at Widget Incorporated, thought about this and wondered how to could come up with a way to solve all three problems. They believe they have. It’s called “Injammies Technology”, an ASP.NET add-on library that ensures code reusability, cross-browser compatibility and low overhead.
It’s exclusive to web applications designed and built by Widget Incorporated. For examples of sites built with this exciting new technology look for the “Built with Injammies Technology” logo on the Widget Incorporated portfolio pages. For more information call Widget Incorporated on 1-800-470-9073 or email firstname.lastname@example.org.
Contact: Roger L. Main