Advance versions of programming languages & frameworks are adding value to website development! Website development is gaining because of regular updates in technologies due to increasing demands of online business for most unique presentations and easy functionality.
Website development using ASP.NET framework is well known in the web development and its introduction after ASP has shown regular development phases. All over the world developers are enjoying its latest versions at regular intervals of time. ASP.NET is popular web application framework of Microsoft, since its inception in year 2002 with version 1.0; developers are using this exclusive technology to develop web applications as well as websites and various web services.
Every new feature in update version produces effective changes in website look as well functionality that helps ultimate user for better presentation of product and services online. Ultimately progressions in technologies also help in online business development such as professional developers use to get new avenues for earning more by providing fresh & easy to use websites to their clients.
So far ASP.NET has introduced its five updated versions with new added features in each version.
* It was first commenced to web world with version 1.0 in 2002 with Visual Studio .NET,
* In 2003 version 1.1 with Windows Server 2003 and Visual Studio .NET 2003,
* In 2005 version 2.0 with Visual Studio 2005, Visual Web Developer Express and SQL Server 2005,
* In 2007 version 3.5 released with Windows Server 2008 and Visual Studio 2008,
* In 2008 version 3.5 service pack released with Visual Studio 2008 Service Pack 1
ASP.NET allows developers for web application development to use fully featured languages like VB.NET and C# (C-Sharp). Feature of “web services” is unique by ASP.NET, class library, XML support and complete compatibility with other programming languages.
Read More..
Showing posts with label web application framework. Show all posts
Showing posts with label web application framework. Show all posts
Monday, December 22, 2008
Tuesday, December 16, 2008
ASP.NET Development: MVC vs. Web Forms
ASP.NET Web Forms
ASP.NET Web forms is a mature technology that runs many large scale websites and is the traditional style of ASP.NET web development. Starting in the .NET framework version 1.0 it is the first technology where Microsoft made an effort to make web development very robust and much more simple. The web forms declarative syntax plus the event driven model allows you to take full advantage of visual designers by drag and dropping the controls onto ASP.NET pages and then writing code against them, much like Windows style development. This makes web forms development very enticing for a wide range of developers on both Windows and other platforms, where drag and drop development via visual designers is common and also provides a separation of web content and web page GUI logic. The key features of web forms include:
* Mature technology
* Rich toolset & controls
* Event driven model
* Easy state management
* Abstracts HTTP
* Feels like Windows development
ASP.NET MVC
MVC (Model View Controller) isn’t a Microsoft technology (and, it’s not even new). , it’s a pattern for web page creation that’s been around for some time now in other frameworks and just recently implemented in ASP.NET. As a developer using MVC you can get a ‘closer to the metal’ experience and finely tuned control of the HTML output, which will be exactly as you define it. Whereas web forms renders output based on your selections of controls and code, MVC is primarily your code with some HTML interspersed, so you get control of each pixel that’s rendered.
The three features of MVC, the model, view and controller are described here…
* The Model can be thought of as the data. This is going to be your fat layer, with all the goodies in it.
* The View is the UI representation of the Model. The view will render the model along with HTML, JavaScript and other page elements.
* The Controller chooses the view to be rendered and responds to user input. The view also manipulates the model, as needed, so the controller is the component that ties the Model and View together. The controller will be the most lightweight code-wise of the three.
As you can see, the MVC approach requires you to work with three objects rather than just one object (the page object) as web forms does. This object trio does give you some advantages over the traditional model:
* It’s testable, you can unit test easily
* Clear separation of concerns
* Control your output exactly
* Map URLs logically or dynamically
* Supports many web forms features (auth, caching, etc…)
* More geeky, higher coolness factor
Read More...
ASP.NET Web forms is a mature technology that runs many large scale websites and is the traditional style of ASP.NET web development. Starting in the .NET framework version 1.0 it is the first technology where Microsoft made an effort to make web development very robust and much more simple. The web forms declarative syntax plus the event driven model allows you to take full advantage of visual designers by drag and dropping the controls onto ASP.NET pages and then writing code against them, much like Windows style development. This makes web forms development very enticing for a wide range of developers on both Windows and other platforms, where drag and drop development via visual designers is common and also provides a separation of web content and web page GUI logic. The key features of web forms include:
* Mature technology
* Rich toolset & controls
* Event driven model
* Easy state management
* Abstracts HTTP
* Feels like Windows development
ASP.NET MVC
MVC (Model View Controller) isn’t a Microsoft technology (and, it’s not even new). , it’s a pattern for web page creation that’s been around for some time now in other frameworks and just recently implemented in ASP.NET. As a developer using MVC you can get a ‘closer to the metal’ experience and finely tuned control of the HTML output, which will be exactly as you define it. Whereas web forms renders output based on your selections of controls and code, MVC is primarily your code with some HTML interspersed, so you get control of each pixel that’s rendered.
The three features of MVC, the model, view and controller are described here…
* The Model can be thought of as the data. This is going to be your fat layer, with all the goodies in it.
* The View is the UI representation of the Model. The view will render the model along with HTML, JavaScript and other page elements.
* The Controller chooses the view to be rendered and responds to user input. The view also manipulates the model, as needed, so the controller is the component that ties the Model and View together. The controller will be the most lightweight code-wise of the three.
As you can see, the MVC approach requires you to work with three objects rather than just one object (the page object) as web forms does. This object trio does give you some advantages over the traditional model:
* It’s testable, you can unit test easily
* Clear separation of concerns
* Control your output exactly
* Map URLs logically or dynamically
* Supports many web forms features (auth, caching, etc…)
* More geeky, higher coolness factor
Read More...
Wednesday, December 10, 2008
Microsoft Releases First BizTalk 2009 Server Beta
Microsoft today released the public beta of BizTalk Server 2009 along with modules aimed at simplifying RFID deployments.
The BizTalk Server 2009 beta is the first public test version of Microsoft's latest services oriented architecture (SOA)-based integration platform. Microsoft indicated in September that the beta release was imminent. The live version is still on pace to ship in the first half of 2009, said Burley Kawasaki, a director with Microsoft's connected systems division.
"It's a feature complete release," Kawasaki said. "We're looking forward to gaining a lot more feedback on the release as part of finalizing it." The beta is available for download from Microsoft's Connect Web site to existing BizTalk customers subscribing to Microsoft's Software Assurance licensing program.
There are no major surprises in the release, commented Forrester analyst Ken Vollmer, but it is an important upgrade. "BizTalk has been widely used for low-end b-to-b connectivity, but it's gradually maturing and growing into a much more capable product in the enterprise integration space," Vollmer said.
BizTalk Server 2009 supports the latest versions of Microsoft's platform, notably the Windows Communications Foundation (WCF) component of the .NET Framework 3.5 SP1. With that comes support for Visual Studio 2008 SP1 and the latest releases of SQL Server and Windows Server. It also will support native Hyper-V, improved clustering, improved failover clustering, and added adaptors and host integration interfaces. It has a new registry based on the UDDI 3.0 specifications.
Read More...
The BizTalk Server 2009 beta is the first public test version of Microsoft's latest services oriented architecture (SOA)-based integration platform. Microsoft indicated in September that the beta release was imminent. The live version is still on pace to ship in the first half of 2009, said Burley Kawasaki, a director with Microsoft's connected systems division.
"It's a feature complete release," Kawasaki said. "We're looking forward to gaining a lot more feedback on the release as part of finalizing it." The beta is available for download from Microsoft's Connect Web site to existing BizTalk customers subscribing to Microsoft's Software Assurance licensing program.
There are no major surprises in the release, commented Forrester analyst Ken Vollmer, but it is an important upgrade. "BizTalk has been widely used for low-end b-to-b connectivity, but it's gradually maturing and growing into a much more capable product in the enterprise integration space," Vollmer said.
BizTalk Server 2009 supports the latest versions of Microsoft's platform, notably the Windows Communications Foundation (WCF) component of the .NET Framework 3.5 SP1. With that comes support for Visual Studio 2008 SP1 and the latest releases of SQL Server and Windows Server. It also will support native Hyper-V, improved clustering, improved failover clustering, and added adaptors and host integration interfaces. It has a new registry based on the UDDI 3.0 specifications.
Read More...
Tuesday, December 9, 2008
Software coders turn to Ruby
Some of the most agile and robust programming in New England’s tech sector is now done in alternatives to status quo programming languages. Sun Microsystems Inc.’s Java and variations of 30-year-old C still dominate surveys of popular code languages, but adventurous developers are experimenting with relatively obscure languages, and getting powerful results.
Many coders believe Ruby on Rails may be poised to make a dent in Java’s dominance on the front end of web applications. For powerful back-end processes, a handful of developers are turning to Erlang. Developed in the 1980s by the communications company Ericsson, this programming language has developer communities buzzing.
“This is what geeks do. They discover something and then someone becomes a fanatic for it,” said Will Koffel, CTO at Sermo Inc. The Cambridge software company uses component-based Ruby on top of the Rails framework to quickly write and test rich new capabilities in its collaborative application for physicians.
Read More...
Many coders believe Ruby on Rails may be poised to make a dent in Java’s dominance on the front end of web applications. For powerful back-end processes, a handful of developers are turning to Erlang. Developed in the 1980s by the communications company Ericsson, this programming language has developer communities buzzing.
“This is what geeks do. They discover something and then someone becomes a fanatic for it,” said Will Koffel, CTO at Sermo Inc. The Cambridge software company uses component-based Ruby on top of the Rails framework to quickly write and test rich new capabilities in its collaborative application for physicians.
Read More...
Saturday, December 6, 2008
10 Dirty Little Web Development Tricks
1. I finally got work to switch from CVS to SVN o.O I finally got us to use "svn up" for staging, but not yet for production… We’re using "svn export --force" for production, which I guess is kind of nice, but afaik it doesn’t delete any files that were deleted in the repository… or if it does, then it also probably ends up deleting any uploaded/cached files as well.
2. I like using the CSS reset from Eric Meyer, but certain people at certain places I’ve worked at are doing well if they can remember an id is supposed to be unique on a page & that the class attribute is a space separated list (not a single value!) that can be used for more than CSS >.< … Granted, a particular brand of browser is doing good if it can figure out how to apply multiply classed CSS definitions to an element (i.e. .class1.class2 { color: #00f; } should be applied to).
3. Kind of have system & static stuff separated at my current place of employment - templates, css, etc go into a templates directory under htdocs & people are too scared to use a framework or an index router >.< My preference is a framework that can handle this (see Symfony or ZF)
4. I don’t drink coffee, but it’s a nice idea - I’ve been drinking caffeine (in the form of pop) before going to bed for years… It helps me go to sleep. I have been drinking XS (no, it doesn’t use sugar - it uses Ace-K as a sweetener, uses B vitamins for the boost [similar to that 5 hour energy drink], and has lots of yummy flavors) to prolong the time before I need to get to sleep. Drinking 1 right before bed can also help give a boost in the morning.
5. Underscores are nifty, but I think he’s missing the boat - generally speaking, come up with a useful convention for letting the file system organize files in general… underscores are great, but other things deserve organization as well - i.e. date based data output should be done in YYYY-MM-DD format for automatic sorting as another example.
Read More..
2. I like using the CSS reset from Eric Meyer, but certain people at certain places I’ve worked at are doing well if they can remember an id is supposed to be unique on a page & that the class attribute is a space separated list (not a single value!) that can be used for more than CSS >.< … Granted, a particular brand of browser is doing good if it can figure out how to apply multiply classed CSS definitions to an element (i.e. .class1.class2 { color: #00f; } should be applied to
3. Kind of have system & static stuff separated at my current place of employment - templates, css, etc go into a templates directory under htdocs & people are too scared to use a framework or an index router >.< My preference is a framework that can handle this (see Symfony or ZF)
4. I don’t drink coffee, but it’s a nice idea - I’ve been drinking caffeine (in the form of pop) before going to bed for years… It helps me go to sleep. I have been drinking XS (no, it doesn’t use sugar - it uses Ace-K as a sweetener, uses B vitamins for the boost [similar to that 5 hour energy drink], and has lots of yummy flavors) to prolong the time before I need to get to sleep. Drinking 1 right before bed can also help give a boost in the morning.
5. Underscores are nifty, but I think he’s missing the boat - generally speaking, come up with a useful convention for letting the file system organize files in general… underscores are great, but other things deserve organization as well - i.e. date based data output should be done in YYYY-MM-DD format for automatic sorting as another example.
Read More..
Friday, November 28, 2008
How Microsoft blew its own RIA invention
Cast your mind back to the year 2000. Microsoft has just announced its .NET Framework, complete with a new language called C# - that was in July, at the Orlando Professional Developers Conference.
A couple of months later, Mark Anders and Scott Guthrie from Microsoft's ASP+ team turned up at the Wrox Web Developer Conference in Las Vegas. Remember ASP+? This was the pre-release name for what became ASP.NET, the web application framework built on .NET.
Anders and Guthrie presented their new technology in the Wrox keynote, following which I interviewed them. They were absolutely the key people. "We started the team about two-and-half years ago. At the beginning it was just the two of us, working on it," said Guthrie.
Was ASP+ based on .NET from the beginning? "No," said Anders. "There were a number of groups around Microsoft that were looking at how we could move the programming model forward. We were on the IIS team; we had just shipped IIS 4.0, and thought we could do a lot better for web development. The tools team thought that they needed to make things simpler. We came up with some stuff, showed it to the tools team. They were working with the runtime team, we liked what the runtime team was doing, and started doing it like that."
Anders later revealed that the first ASP+ experiments were done in Java.
We also discussed how.NET components hosted in the browser might become a more secure alternative to ActiveX. "That is there today," said Anders. "If you create controls using WinForms, those can be hosted in IE [Internet Explorer] and run within the security sandbox. It's not through ActiveX hosting.
"As your binding to code within one of those components that comes down in the browser, if it's not present on the machine it will be downloaded. We have a great incremental download and deployment story. We expect it to be very popular."
Good idea, but it never really happened. Microsoft got security cold feet, and ended up crippling the feature in the 1.0 Framework so that Windows Forms controls did not run at all in the default Internet Zone. This was fixed in 1.1, but web developers disliked the .NET dependency and the fact that it only worked with IE and Windows.
Read More..
A couple of months later, Mark Anders and Scott Guthrie from Microsoft's ASP+ team turned up at the Wrox Web Developer Conference in Las Vegas. Remember ASP+? This was the pre-release name for what became ASP.NET, the web application framework built on .NET.
Anders and Guthrie presented their new technology in the Wrox keynote, following which I interviewed them. They were absolutely the key people. "We started the team about two-and-half years ago. At the beginning it was just the two of us, working on it," said Guthrie.
Was ASP+ based on .NET from the beginning? "No," said Anders. "There were a number of groups around Microsoft that were looking at how we could move the programming model forward. We were on the IIS team; we had just shipped IIS 4.0, and thought we could do a lot better for web development. The tools team thought that they needed to make things simpler. We came up with some stuff, showed it to the tools team. They were working with the runtime team, we liked what the runtime team was doing, and started doing it like that."
Anders later revealed that the first ASP+ experiments were done in Java.
We also discussed how.NET components hosted in the browser might become a more secure alternative to ActiveX. "That is there today," said Anders. "If you create controls using WinForms, those can be hosted in IE [Internet Explorer] and run within the security sandbox. It's not through ActiveX hosting.
"As your binding to code within one of those components that comes down in the browser, if it's not present on the machine it will be downloaded. We have a great incremental download and deployment story. We expect it to be very popular."
Good idea, but it never really happened. Microsoft got security cold feet, and ended up crippling the feature in the 1.0 Framework so that Windows Forms controls did not run at all in the default Internet Zone. This was fixed in 1.1, but web developers disliked the .NET dependency and the fact that it only worked with IE and Windows.
Read More..
Thursday, November 27, 2008
Microsoft .NET Framework 3.5 Launched
Microsoft .NET Framework 3.5
Brief Description::
Microsoft .NET Framework 3.5 contains many new features building incrementally upon .NET Framework 2.0 and 3.0, and includes .NET Framework 2.0 service pack 1 and .NET Framework 3.0 service pack 1.
Overview
.NET Framework 3.5 builds incrementally on the new features added in .NET Framework 3.0. For example, feature sets in Windows Workflow Foundation (WF), Windows Communication Foundation (WCF), Windows Presentation Foundation (WPF) and Windows CardSpace. In addition, .NET Framework 3.5 contains a number of new features in several technology areas which have been added as new assemblies to avoid breaking changes. They include the following:
* Deep integration of Language Integrated Query (LINQ) and data awareness. This new feature will let you write code written in LINQ-enabled languages to filter, enumerate, and create projections of several types of SQL data, collections, XML, and DataSets by using the same syntax.
* ASP.NET AJAX lets you create more efficient, more interactive, and highly-personalized Web experiences that work across all the most popular browsers.
* New Web protocol support for building WCF services including AJAX, JSON, REST, POX, RSS, ATOM, and several new WS-* standards.
* Full tooling support in Visual Studio 2008 for WF, WCF, and WPF, including the new workflow-enabled services technology.
* New classes in .NET Framework 3.5 base class library (BCL) that address many common customer requests.
IMPORTANT:
* If you have installed earlier pre-release versions of .NET Framework 3.5, then you must uninstall them prior to running this installation by using Add or Remove Programs.
Read More..
Brief Description::
Microsoft .NET Framework 3.5 contains many new features building incrementally upon .NET Framework 2.0 and 3.0, and includes .NET Framework 2.0 service pack 1 and .NET Framework 3.0 service pack 1.
Overview
.NET Framework 3.5 builds incrementally on the new features added in .NET Framework 3.0. For example, feature sets in Windows Workflow Foundation (WF), Windows Communication Foundation (WCF), Windows Presentation Foundation (WPF) and Windows CardSpace. In addition, .NET Framework 3.5 contains a number of new features in several technology areas which have been added as new assemblies to avoid breaking changes. They include the following:
* Deep integration of Language Integrated Query (LINQ) and data awareness. This new feature will let you write code written in LINQ-enabled languages to filter, enumerate, and create projections of several types of SQL data, collections, XML, and DataSets by using the same syntax.
* ASP.NET AJAX lets you create more efficient, more interactive, and highly-personalized Web experiences that work across all the most popular browsers.
* New Web protocol support for building WCF services including AJAX, JSON, REST, POX, RSS, ATOM, and several new WS-* standards.
* Full tooling support in Visual Studio 2008 for WF, WCF, and WPF, including the new workflow-enabled services technology.
* New classes in .NET Framework 3.5 base class library (BCL) that address many common customer requests.
IMPORTANT:
* If you have installed earlier pre-release versions of .NET Framework 3.5, then you must uninstall them prior to running this installation by using Add or Remove Programs.
Read More..
Wednesday, November 26, 2008
Disadvantages of the ASP.NET MVC Framework
The ASP.NET MVC framework is a new and lightweight architectural pattern still in its infancy. Although evolving from Preview 1 to Preview 4, there are still a great many supplements and enhancements necessary. So far, there have not been any real scenarios of ASP.NET applications putting it into practice. Now, I'm going to use scraps of code to list the disadvantages (immaturity) of ASP.NET MVC as far as I know. This is the fourth part of a four-part series that compares ASP.NET Web Forms with ASP.NET MVC.
(1) Writing View Contents the Old ASP-Like Way
As you may have noticed above, it uses an inline mode, foreach, to render the .aspx page’s contents. Indeed, code generated in the above mode is spotless whether in the case of cleanness or from the angle of self definition. But……yes, as you have seen, it’s the original ASP mode, just switched to another term—the ASP.NET MVC-styled template! Isn't it ironic? Yet, this is indeed the fact.
Since a flock of developers are now ready to embrace ASP.NET MVC without hesitation, are they also ready to deal with the old-style inline mode? Due to the features of ASP.NET MVC (mainly a ViewData transferred from the Controller to the View), the true ASP.NET MVC template syntax requires a plus CAST, such as the following (of course, you can also use the strong-typed ViewData supported by ASP.NET MVC, which can help to avoid such a cast operation).
Read More..
(1) Writing View Contents the Old ASP-Like Way
As you may have noticed above, it uses an inline mode, foreach, to render the .aspx page’s contents. Indeed, code generated in the above mode is spotless whether in the case of cleanness or from the angle of self definition. But……yes, as you have seen, it’s the original ASP mode, just switched to another term—the ASP.NET MVC-styled template! Isn't it ironic? Yet, this is indeed the fact.
Since a flock of developers are now ready to embrace ASP.NET MVC without hesitation, are they also ready to deal with the old-style inline mode? Due to the features of ASP.NET MVC (mainly a ViewData transferred from the Controller to the View), the true ASP.NET MVC template syntax requires a plus CAST, such as the following (of course, you can also use the strong-typed ViewData supported by ASP.NET MVC, which can help to avoid such a cast operation).
Read More..
Monday, November 17, 2008
What is difference between ExecuteReader, ExecuteNonQuery and ExecuteScalar.
1. ExecuteReader : Use for accessing data. It provides a forward-only, read-only, connected recordset.
2. ExecuteNonQuery : Use for data manipulation, such as Insert, Update, Delete.
3. ExecuteScalar : Use for retriving 1 row 1 col. value., i.e. Single value. eg: for retriving aggregate function. It is faster than other ways of retriving a single value from DB.
Read More..
2. ExecuteNonQuery : Use for data manipulation, such as Insert, Update, Delete.
3. ExecuteScalar : Use for retriving 1 row 1 col. value., i.e. Single value. eg: for retriving aggregate function. It is faster than other ways of retriving a single value from DB.
Read More..
Friday, November 14, 2008
The Future of WebForms And ASP.NET MVC
ASP.NET Themes
If you watch the ASP.NET 4.0 Roadmap talk at PDC, you’ll see that there are five main areas of investment that the ASP.NET team is working on. I’ll provide a non-comprehensive brief summary of the five here.
Core Infrastructure
With our core infrastructure, we’re looking to address key customer pain points and
improve scale and performance.
One feature towards this goal is cache extensibility which will allow plugging in other cache products such as Velocity as a cache provider. We’ll also enhance ASP.NET Session State APIs. There are other scalability investments I don’t even personally understand all too deeply. ;)
To learn more about our cache extensibility plans, check out this PDC talk by Stefan Schackow.
Web Forms
In WebForms, we’re looking to address Client IDs which allow developers to control the id attribute value rendered by server controls. We’re adding support for URL routing with Web Forms. We’re planning to improve ViewState management by providing fine grain control over it. And we’re making investments in making our controls more CSS friendly. There are many other miscellaneous improvements to various control we’re making that would require me to query and filter the bug database to list, and I’m too lazy to do that right now.
AJAX
With Ajax, we’re implementing client side templates and data binding. Our team now owns the Ajax Control Toolkit so we’re looking at opportunities to possibly roll some of those server controls into the core framework. And of course, we’ve added jQuery to our offerings along with jQuery Intellisense.
To see more about our investments here, check out Bertrand Le Roy’s Ajax talk at PDC.
Data and Dynamic Data
In Dynamic Data (which technically could fall in the Web Forms bucket) we’re looking to add support for an abstract data layer which would allow for POCO scaffolding. We’re implementing many-to-many relationships, enhanced filtering, enhanced meta-data, and adding new field templates.
There’s a lot of cool stuff happening here. To get more details on this, check out Scott Hunter’s Dynamic Data talk at PDC.
ASP.NET MVC
We’re still working on releasing 1.0. In the future, we hope to leverage some of the Dynamic Data work into ASP.NET MVC.
Notice here that ASP.NET MVC is just one of these five areas we’re investing in moving forward. It’s not somehow starving our efforts in other areas.
Read More..
If you watch the ASP.NET 4.0 Roadmap talk at PDC, you’ll see that there are five main areas of investment that the ASP.NET team is working on. I’ll provide a non-comprehensive brief summary of the five here.
Core Infrastructure
With our core infrastructure, we’re looking to address key customer pain points and
improve scale and performance.
One feature towards this goal is cache extensibility which will allow plugging in other cache products such as Velocity as a cache provider. We’ll also enhance ASP.NET Session State APIs. There are other scalability investments I don’t even personally understand all too deeply. ;)
To learn more about our cache extensibility plans, check out this PDC talk by Stefan Schackow.
Web Forms
In WebForms, we’re looking to address Client IDs which allow developers to control the id attribute value rendered by server controls. We’re adding support for URL routing with Web Forms. We’re planning to improve ViewState management by providing fine grain control over it. And we’re making investments in making our controls more CSS friendly. There are many other miscellaneous improvements to various control we’re making that would require me to query and filter the bug database to list, and I’m too lazy to do that right now.
AJAX
With Ajax, we’re implementing client side templates and data binding. Our team now owns the Ajax Control Toolkit so we’re looking at opportunities to possibly roll some of those server controls into the core framework. And of course, we’ve added jQuery to our offerings along with jQuery Intellisense.
To see more about our investments here, check out Bertrand Le Roy’s Ajax talk at PDC.
Data and Dynamic Data
In Dynamic Data (which technically could fall in the Web Forms bucket) we’re looking to add support for an abstract data layer which would allow for POCO scaffolding. We’re implementing many-to-many relationships, enhanced filtering, enhanced meta-data, and adding new field templates.
There’s a lot of cool stuff happening here. To get more details on this, check out Scott Hunter’s Dynamic Data talk at PDC.
ASP.NET MVC
We’re still working on releasing 1.0. In the future, we hope to leverage some of the Dynamic Data work into ASP.NET MVC.
Notice here that ASP.NET MVC is just one of these five areas we’re investing in moving forward. It’s not somehow starving our efforts in other areas.
Read More..
Thursday, November 13, 2008
How To Localize Your Application Using String Tables
Until a couple of years ago, most software applications were released in English. Unfortunately for us the developers, nowadays, many customers require that that the product they purchase, will be localized to a specific language (other than English). I know, for instance, that there is a European law which requires healthcare products to be localized to the European market (starting from 2009 or 2010). Because this article is about how to localize your application using string tables, I recommend you to first read about a free tool which helps you extract hard coded strings to string tables. Don’t go any further before you also read about how to generate public properties for string tables, you must read it.
Setting up a String Table
I assume that you already have some user interface which needs to be localized, I will demonstrate this process with Windows Forms but it doesn’t matter what UI framework is being used. The first thing to do is to add a string table, you can add it to your UI project or to another project (if it will be used from other assemblies as well).
Read More..
Setting up a String Table
I assume that you already have some user interface which needs to be localized, I will demonstrate this process with Windows Forms but it doesn’t matter what UI framework is being used. The first thing to do is to add a string table, you can add it to your UI project or to another project (if it will be used from other assemblies as well).
Read More..
Wednesday, November 12, 2008
ASP.NET Web Forms Weaknesses
The Weakness of ASP.NET Web Forms
On the whole, the weakness of the traditional ASP.NET Web Forms solution mainly lies in the following four aspects. Let's check each of them one by one.
(1) ViewState and Postbacks
Maybe the most disputable point people often bring forward about ASP.NET Web Forms relates to ViewState and Postbacks. To introduce an event-driven approach and overcome the stateless nature (and also obstacle) of HTTP protocol to simulate the old Windows form model development experience, ASP.NET Web Forms introduces ViewState and Postback. The end result is both ViewState and Postbacks have caused lots of problems and increased the complexity of web application development. Even simple web pages can produce a ViewState larger than 100KB in size that heavily affects the performance of the application sometimes.
Is ViewState is a must have in an ASP.NET application? In fact, most existing web pages usually feature a good many hyperlinks. When you click one of the links, you will be navigated to a new page. Since clicking the links will lead you to another page, what is the use of ViewState within the page? In practice, when I start to write a new web project, the first thing I do is turn off the enableViewState (and sometimes enableSessionState) parameter from inside the Web.config file.
Some may ask me what sense there is to using Web Forms since I turn off ViewState. My answer is: there are many reasons. Web Form provides a control model, and so users can take advantage of the easy-to-grasp mode to set/get the value of a text box, and also, they can use many button events easily to write related event handlers to trigger various business logics. Moreover, using Web Forms is simple and clear.
Well, without ViewState why can you use the events of the controls? Of course, you can if the events are not complex ones. Here is an example. The TextBox's TextChange event belongs to complex events, as well as the Command event of the GridView control. However, the click event of a Button control is the "simple event."
As with the event, there are also complex states and simple ones. Take, again, for example: the state of each sub-control within each line inside the GridView control is a "complex state," while the Text property of a TextBox control belongs to a "simple state." "Complex states" and "complex events" require ViewState, while the simple ones do not. So, why not try to use simple states and events instead of complex ones?
One of the most prominent and significant features of ASP.NET Web Forms lies in its powerful (and complex) component model. Inside this model was introduced something named "page life cycle." Many people threw stones at it and accused it of killing system performance. In essence, this complex life-cycle does, at some times, run without any efficient result again and again. However, assuming that the ASP.NET "page life cycle" kills performance is not right.
Read More..
Monday, November 10, 2008
New version of Enterprise Service Bus software extends the Microsoft .NET Platform
Neudesic, a leading provider of business solutions that leverage the capabilities of the Microsoft product line, announced today the release of version 2।0 of Neuron-ESB. Neuron-ESB is an Enterprise Service Bus that extends the Microsoft Platform by providing real-time messaging, integration and web service management. Neuron-ESB accelerates SOA adoption by helping companies successfully implement real-time integration across their enterprise, allowing timely response to changing events within their business.
Neuron-ESB is built on the Microsoft Windows Communication Framework (WCF) technology to provide real-time reliable messaging options for companies adopting SOA। Neuron-ESB manages all communication over the bus by sending messages over "Topics" using a publish-subscribe pattern and supports federated, geographic deployments। Neuron-ESB helps companies administer and automate complex tasks and is proven to significantly reduce the infrastructure, development, training and long term support costs for businesses developing SOA solutions.
"Neuron-ESB provides the messaging backbone for all of our critical applications," said Jeffrey Sullivan, Chief Information Officer of ThinkCash. "Neuron-ESB allowed us to leverage our developers much more effectively while providing us the ability to go to market quickly with new solutions. We were able to shift our service development from the architect role to the more ubiquitous developer role while, decreasing our deployment time of new services by 50%. We started with just 1 developer who received 4 days of Neuron-ESB training. Within 6 months and no additional training, we had a 15X increase in the number of our internal developers who were able to use Neuron-ESB."
Read More..
Neuron-ESB is built on the Microsoft Windows Communication Framework (WCF) technology to provide real-time reliable messaging options for companies adopting SOA। Neuron-ESB manages all communication over the bus by sending messages over "Topics" using a publish-subscribe pattern and supports federated, geographic deployments। Neuron-ESB helps companies administer and automate complex tasks and is proven to significantly reduce the infrastructure, development, training and long term support costs for businesses developing SOA solutions.
"Neuron-ESB provides the messaging backbone for all of our critical applications," said Jeffrey Sullivan, Chief Information Officer of ThinkCash. "Neuron-ESB allowed us to leverage our developers much more effectively while providing us the ability to go to market quickly with new solutions. We were able to shift our service development from the architect role to the more ubiquitous developer role while, decreasing our deployment time of new services by 50%. We started with just 1 developer who received 4 days of Neuron-ESB training. Within 6 months and no additional training, we had a 15X increase in the number of our internal developers who were able to use Neuron-ESB."
Read More..
ASP.NET BLOB & Thumbnail Controls 2.0 description
A set of ASP.NET server controls for rendering 2 way data bindable images or other files on the fly from SQL BLOB, programmable download links and many BLOB and file related operations without requiri
A set of ASP.NET server controls for developing SQL BLOB & Thumbnail related web applications in the most efficient, organized and object oriented manner without requiring you writing any codes or ashx http handler files. A set of controls: BlobImageButton, BlobImage, BlobThumbnail, BlobIFrame, BlobButton, BlobHyperlink. BlobImageButton, inherited from ImageButton, will behave exactly like a standard image button with extra byte[] type property named BlobData. The image will be rendered from the value of this byte[] property instead of ImageURL property. Also you can display the image as a thumbnail by setting a checkbox. BlobThumbnail Control will display a thumbnail and clicking the thumbnail will show a popup window with the full sized image or prompt Download dialog box. BlobButton and BlobHyperlink controls are used to display a Download prompt/dialog to download the byte[] content as a file. You can program those controls to create a secured download link so that your visitor won?t see the real location of the file in your server, good for developers who are selling digital products like eBooks or softwares. SpiceLogic BLOB & Thumbnail Control suit will not only display your Images directly from your SQL Blob, but also it will create Thumbnails on the fly. The power of this control is its BLOB 2 way data binding feature. Now, you can simply bind the byte[] BlobData property of this control to your VarBinary or any byte[] datatype of your DataSource and place this control in your DataBound Container Control like GridView or DetailsView. You can also Update/Insert new Blob records using this control (Setting Upload Mode=true). UploadMode will show a Upload form element and upload button element, and that gives you the power to upload files directly to the BlobData property. This control never creates any temporary file in your server so you won?t need to worry about setting any WRITE permission to your web folders. A very straight forward and friendly control.
Read More..
A set of ASP.NET server controls for developing SQL BLOB & Thumbnail related web applications in the most efficient, organized and object oriented manner without requiring you writing any codes or ashx http handler files. A set of controls: BlobImageButton, BlobImage, BlobThumbnail, BlobIFrame, BlobButton, BlobHyperlink. BlobImageButton, inherited from ImageButton, will behave exactly like a standard image button with extra byte[] type property named BlobData. The image will be rendered from the value of this byte[] property instead of ImageURL property. Also you can display the image as a thumbnail by setting a checkbox. BlobThumbnail Control will display a thumbnail and clicking the thumbnail will show a popup window with the full sized image or prompt Download dialog box. BlobButton and BlobHyperlink controls are used to display a Download prompt/dialog to download the byte[] content as a file. You can program those controls to create a secured download link so that your visitor won?t see the real location of the file in your server, good for developers who are selling digital products like eBooks or softwares. SpiceLogic BLOB & Thumbnail Control suit will not only display your Images directly from your SQL Blob, but also it will create Thumbnails on the fly. The power of this control is its BLOB 2 way data binding feature. Now, you can simply bind the byte[] BlobData property of this control to your VarBinary or any byte[] datatype of your DataSource and place this control in your DataBound Container Control like GridView or DetailsView. You can also Update/Insert new Blob records using this control (Setting Upload Mode=true). UploadMode will show a Upload form element and upload button element, and that gives you the power to upload files directly to the BlobData property. This control never creates any temporary file in your server so you won?t need to worry about setting any WRITE permission to your web folders. A very straight forward and friendly control.
Read More..
Advanced ASP.NET AJAX Server Controls For .NET Framework 3.5
ASP.NET AJAX server controls can encapsulate even the most powerful AJAX functionality, helping you build more elegant, maintainable, and scalable applications. This is the first comprehensive, code-rich guide to custom ASP.NET AJAX server controls for experienced ASP.NET developers. Unlike other books on ASP.NET AJAX, this book focuses solely on server control development and reflects the significant improvements in ASP.NET 3.5 AJAX and the latest Visual Studio 2008 features for streamlining AJAX development
Adam Calderon and Joel Rumerman first review the core Microsoft AJAX Library and JavaScript techniques needed to support a rich client-side experience. Next, they build upon these techniques showing how to create distributable AJAX-enabled controls that include rich browser-independent JavaScript client-side functionality. The authors thoroughly explain both the JavaScript and .NET aspects of control development and how these two distinct environments come together to provide a foundation for building a rich user experience using ASP.NET AJAX.
Create object-oriented cross-browser JavaScript that supports .NET style classes, interfaces, inheritance, and method overloading
Work with components, behaviors, and controls, and learn how they relate to DOM elements.
Read More..
Adam Calderon and Joel Rumerman first review the core Microsoft AJAX Library and JavaScript techniques needed to support a rich client-side experience. Next, they build upon these techniques showing how to create distributable AJAX-enabled controls that include rich browser-independent JavaScript client-side functionality. The authors thoroughly explain both the JavaScript and .NET aspects of control development and how these two distinct environments come together to provide a foundation for building a rich user experience using ASP.NET AJAX.
Create object-oriented cross-browser JavaScript that supports .NET style classes, interfaces, inheritance, and method overloading
Work with components, behaviors, and controls, and learn how they relate to DOM elements.
Read More..
Friday, November 7, 2008
Google Maps and ASP.NET
What makes the service even better is the availability of the Google Maps API (Application Programming Interface) as a free Beta service. The API allows developers to embed Google Maps in their custom applications. It also allows them to overlay information on the map and customize the map to their needs. As I write this article there are quite a few sites that utilize Google Maps, and more and more of them are appearing by the day.
The API by itself is pretty straightforward and easy to use; however, it requires the developer to have a good command of JavaScript because it extensively relies on client-side Java scripting. In this article we will be looking at building a custom ASP.NET server control that would allow a .NET developer to harness the power of Google Maps in the code-behind model. We will see how to accomplish most of the functionality exposed by Google Maps using this control, and we'll also see how to data bind the control, thereby allowing developers to easily build data-driven custom ASP.NET Web applications. The control would eliminate the need for the developer to write any JavaScript to accomplish most of the Google Map functionality.
Some Google Maps Basics
Before we get into the details of the ASP.NET control, let's look at the basics of the Google Maps API. A detailed description of the API can be found at www.google.com/apis/maps/documentation/. The first step before using Google Maps is to register for a key with Google (www.google.com/apis/maps/signup.html). This is absolutely free and hardly takes a few minutes. Each Web site that uses Google Maps has to have its own key. Make sure that you go through Google's Terms of Use (www.google.com/apis/maps/terms.html) before you start using Google Maps in your application.
Read More..
The API by itself is pretty straightforward and easy to use; however, it requires the developer to have a good command of JavaScript because it extensively relies on client-side Java scripting. In this article we will be looking at building a custom ASP.NET server control that would allow a .NET developer to harness the power of Google Maps in the code-behind model. We will see how to accomplish most of the functionality exposed by Google Maps using this control, and we'll also see how to data bind the control, thereby allowing developers to easily build data-driven custom ASP.NET Web applications. The control would eliminate the need for the developer to write any JavaScript to accomplish most of the Google Map functionality.
Some Google Maps Basics
Before we get into the details of the ASP.NET control, let's look at the basics of the Google Maps API. A detailed description of the API can be found at www.google.com/apis/maps/documentation/. The first step before using Google Maps is to register for a key with Google (www.google.com/apis/maps/signup.html). This is absolutely free and hardly takes a few minutes. Each Web site that uses Google Maps has to have its own key. Make sure that you go through Google's Terms of Use (www.google.com/apis/maps/terms.html) before you start using Google Maps in your application.
Read More..
ASP.NET Is The Latest Version Of ASP Technology
ASP.NET is the next generation ASP, but it's not an upgraded version of ASP. ASP.NET is an entirely new technology for server-side scripting. It was written from the ground up and is not backward compatible with classic ASP.ASP.NET is the major part of the Microsoft's .NET Framework.
ASP.NET is a server side scripting technology that enables scripts (embedded in web pages) to be executed by an Internet server.
•ASP.NET is a Microsoft Technology
•ASP stands for Active Server Pages
•ASP.NET is a program that runs inside IIS
•IIS (Internet Information Services) is Microsoft's Internet server
•IIS comes as a free component with Windows servers
•IIS is also a part of Windows 2000 and XP Professional
ASP.NET 2.0 improves upon Asp.Net by adding support for several new features and ASP.NET 3.0 is not a new version of ASP.NET. It's just the name for a new ASP.NET 2.0 framework library with support for Windows Presentation Foundation, Windows Communication Foundation, Windows Workflow Foundation; and Windows Card Space.
Benefits of ASP.Net
•ASP.NET has better language support, a large set of new controls and XML based components.
•ASP.NET provides increased performance by running compiled code.
•ASP.NET code is not fully backward compatible with ASP.
•Event-driven programming
•User authentication, with accounts and roles
•Higher scalability
•Easier configuration and deployment
Read More..
ASP.NET is a server side scripting technology that enables scripts (embedded in web pages) to be executed by an Internet server.
•ASP.NET is a Microsoft Technology
•ASP stands for Active Server Pages
•ASP.NET is a program that runs inside IIS
•IIS (Internet Information Services) is Microsoft's Internet server
•IIS comes as a free component with Windows servers
•IIS is also a part of Windows 2000 and XP Professional
ASP.NET 2.0 improves upon Asp.Net by adding support for several new features and ASP.NET 3.0 is not a new version of ASP.NET. It's just the name for a new ASP.NET 2.0 framework library with support for Windows Presentation Foundation, Windows Communication Foundation, Windows Workflow Foundation; and Windows Card Space.
Benefits of ASP.Net
•ASP.NET has better language support, a large set of new controls and XML based components.
•ASP.NET provides increased performance by running compiled code.
•ASP.NET code is not fully backward compatible with ASP.
•Event-driven programming
•User authentication, with accounts and roles
•Higher scalability
•Easier configuration and deployment
Read More..
NET Framework version 3.5 Service Pack 1 provides the following new features and improvements
* ASP.NET Dynamic Data, which provides a rich scaffolding framework that enables rapid data driven development without writing code, and a new addition to ASP.NET AJAX that provides support for managing browser history (back button support). For more information, see What’s New in ASP.NET and Web Development.
* Core improvements to the CLR (common language runtime) that include better layout of .NET Framework native images, opting out of strong-name verification for fully trusted assemblies, improved application startup performance, better generated code that improves end-to-end application execution time, and opting managed code to run in ASLR (Address Space Layout Randomization) mode if supported by the operating system. Additionally, managed applications that are opened from network shares have the same behavior as native applications by running with full trust.
* Performance improvements to WPF (Windows Presentation Foundation), including a faster startup time and improved performance for Bitmap effects. Additional functionality for WPF includes better support for line of business applications, native splash screen support, DirectX pixel shader support, and the new WebBrowser control.
* ClickOnce application publishers can decide to opt out of signing and hashing as appropriate for their scenarios, developers can programmatically install ClickOnce applications that display a customized branding, and ClickOnce error dialog boxes support links to application-specific support sites on the Web.
Read More..
* Core improvements to the CLR (common language runtime) that include better layout of .NET Framework native images, opting out of strong-name verification for fully trusted assemblies, improved application startup performance, better generated code that improves end-to-end application execution time, and opting managed code to run in ASLR (Address Space Layout Randomization) mode if supported by the operating system. Additionally, managed applications that are opened from network shares have the same behavior as native applications by running with full trust.
* Performance improvements to WPF (Windows Presentation Foundation), including a faster startup time and improved performance for Bitmap effects. Additional functionality for WPF includes better support for line of business applications, native splash screen support, DirectX pixel shader support, and the new WebBrowser control.
* ClickOnce application publishers can decide to opt out of signing and hashing as appropriate for their scenarios, developers can programmatically install ClickOnce applications that display a customized branding, and ClickOnce error dialog boxes support links to application-specific support sites on the Web.
Read More..
Thursday, November 6, 2008
AJAX Gauge Control by DevExpress
DevExpress has announced the immediate availability of the ASPxGauge Component Suite for Windows Forms. Built and optimized for Visual Studio .NET, this Gauge control simplifies the way in which developers create and deliver dashboard-style UIs to their customers.
With the DevExpress Gauge control for ASP.NET, you have the following features and options available to you when building your next dashboard-style interface:
- 130 ready to use gauge presets
- 10 stunning visual styles
- 4 individual gauge types including: Circular Gauge, Linear Gauge, State Indicator and Digital Gauge
- Built-in gauge data binding support
- Real-time performance support via its highly optimized architecture
Read More..
With the DevExpress Gauge control for ASP.NET, you have the following features and options available to you when building your next dashboard-style interface:
- 130 ready to use gauge presets
- 10 stunning visual styles
- 4 individual gauge types including: Circular Gauge, Linear Gauge, State Indicator and Digital Gauge
- Built-in gauge data binding support
- Real-time performance support via its highly optimized architecture
Read More..
Tuesday, November 4, 2008
What's new in .NET Framework 3.5 SP1?
SP1 advances the art of application development
The new ADO.NET Entity Framework feature in SP1 offers developers a model-based paradigm and a rich, standards-based framework for creating data-oriented applications shared across multiple applications and platforms. The separation of presentation, data, and business logic used in concert with a single data model will enable developers to spend less time writing plumbing code and more time refining business logic.
SP1 makes data-driven programming easier
SP1 offers developers support for ASP.NET Dynamic Data, which provides a rich scaffolding framework that enables rapid data-driven development. Since ASP.NET takes care of creating the presentation layer, a fully functional Website is output and ready for customization without the developer writing a single line of code. Further, with ADO.NET Data Services, Web developers can create RESTful Web 2.0-style applications that have better server scalability and improved caching support.
SP1 is the fastest and easiest way to deploy Windows applications
With the .NET Framework Client Profile, a small subset of the Framework that powers client applications, developers can offer their end users a dramatically streamlined and rapid application download experience. In addition, improvements in SP1 result in dramatic reductions in cold start times, allowing developers to serve a broader set of customers with varying hardware profiles.
Read More..
The new ADO.NET Entity Framework feature in SP1 offers developers a model-based paradigm and a rich, standards-based framework for creating data-oriented applications shared across multiple applications and platforms. The separation of presentation, data, and business logic used in concert with a single data model will enable developers to spend less time writing plumbing code and more time refining business logic.
SP1 makes data-driven programming easier
SP1 offers developers support for ASP.NET Dynamic Data, which provides a rich scaffolding framework that enables rapid data-driven development. Since ASP.NET takes care of creating the presentation layer, a fully functional Website is output and ready for customization without the developer writing a single line of code. Further, with ADO.NET Data Services, Web developers can create RESTful Web 2.0-style applications that have better server scalability and improved caching support.
SP1 is the fastest and easiest way to deploy Windows applications
With the .NET Framework Client Profile, a small subset of the Framework that powers client applications, developers can offer their end users a dramatically streamlined and rapid application download experience. In addition, improvements in SP1 result in dramatic reductions in cold start times, allowing developers to serve a broader set of customers with varying hardware profiles.
Read More..
Subscribe to:
Posts (Atom)