Cloud computing is Internet-based (“cloud”) development and use of computer technology (”computing“). The cloud is a metaphor for the Internet (based on how it is depicted in computer network diagrams) and is an abstraction for the complex infrastructure it conceals.[1] It is a style of computing in which IT-related capabilities are provided “as a service”,[2] allowing users to access technology-enabled services from the Internet (”in the cloud”)[3] without knowledge of, expertise with, or control over the technology infrastructure that supports them. According to a 2008 paper published by IEEE Internet Computing “Cloud Computing is a paradigm in which information is permanently stored in servers on the Internet and cached temporarily on clients that include desktops, entertainment centers, table computers, notebooks, wall computers, handhelds, sensors, monitors, etc.”
Cloud computing is a general concept that incorporates software as a service (SaaS), Web 2.0 and other recent, well-known technology trends, in which the common theme is reliance on the Internet for satisfying the computing needs of the users.
Microsoft , Google and Amazon has already launch their platform which worked base on the Cloud Computing Architecture. Microsoft Azure Platform , Google Apps Engine and Amazon Web Service are most reasonable example of Cloud Computing .
There are similarities. However, Azure supports any .NET 3.5 language (C#, VB.NET, F# and a number of others), whereas App Engine only supports Python. In addition Microsoft has already announced that eventually you will be able to run native code on Azure opening the door to almost any Language/Framework that runs in Windows (e.g. Java, PERL, PHP).
Google App Engine doesn’t provide local storage. Azure does (although it’s not shared across instances, you have to use the Azure Storage Service for that). I’m not sure what ancillary offerings Google has beside app engine, but Azure provides a number of services above and beyond the hosting service including
* SQL Data (and soon to be Reporting and Analysis) services,
* .NET Services (WF, WCF and Identity services in the cloud),
* Live Framework (too much there for words)
I’m pretty sure I’m missing something there, but it’s 2 in the morning. Basically the big deal here is that Azure has a lot to offer that GAE is lacking currently, and will have more to offer in the upcoming months. So yes it is equal to GAE…and then some.
Read More..
Showing posts with label ASP.NET development. Show all posts
Showing posts with label ASP.NET development. Show all posts
Tuesday, January 6, 2009
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...
Monday, December 1, 2008
Is the Cloud Looking Like HDDVD vs. Blu-Ray?
I was reading through this post from Mary-Jo Foley about cloud computing, but more specifically about approaches to (in this case, data caching) how it gets done. I have to admit, for me, I sort of thought of the cloud options as being "out there" to the point where it just happens - who cares how? But now, after reading this and doing more poking around the 'net, reading articles, etc., I am beginning to wonder if we'll have emerging standards that impact how you develop applications, deploy those applications and support them.
If this ends up being a "war of formats" something like the HDDVD and Blu-Ray format wars, it would seem like this could really cripple adoption of the whole cloud computing model, certainly to the point where you'd have to add a new layer of testing and working with your systems to see what works best.
Mary-Jo's article focused on the cache element - how data is made available in a high-performance environment. It bleeds over into content delivery (since the platforms define it differently), which brings up additional points that you'll want to understand.
Perhaps I'm just misunderstanding, perhaps I'm over-estimating the amount of choice you really have in how things are done "up there" - but it's certainly worth trying to understand and see where the performance, security and implementation differ between options and platforms.
Read More..
If this ends up being a "war of formats" something like the HDDVD and Blu-Ray format wars, it would seem like this could really cripple adoption of the whole cloud computing model, certainly to the point where you'd have to add a new layer of testing and working with your systems to see what works best.
Mary-Jo's article focused on the cache element - how data is made available in a high-performance environment. It bleeds over into content delivery (since the platforms define it differently), which brings up additional points that you'll want to understand.
Perhaps I'm just misunderstanding, perhaps I'm over-estimating the amount of choice you really have in how things are done "up there" - but it's certainly worth trying to understand and see where the performance, security and implementation differ between options and platforms.
Read More..
Sunday, November 23, 2008
Asp.net Development Benefits
Web development is the process by which you can get more features of innovative technology – web design, back end programming and software solution for more business efficiency, simply get more from your website infrastructure by integrating each element. Skilled ASP.NET web developers are available for ASP.NET software development, ASP.NET website development & ASP.NET programming.
Advantages of ASP.NET:
* Any application can talk to a host of other applications, running on diverse technology and hardware, in turn lowering the operation costs. Consider this one case, wherein the stock management system is connected to the accounting system, resulting in ample savings.
* Bring on one platform all your internal applications, your partners as well as your customers.
* Microsoft Visual Studio® .NET and the .NET Framework supports varied languages, in turn helping developers to focus on work at hand instead of trying to learn a new language that can do the job.
* Employees can look for updated information on desktop applications, internet browsers or even mobile devices.
* Optimum speed of development
* Ability of cross platform migration
* High Reliability
* Rigorous Security
* Easy configurations of applications
* Vast and enriched Class library, features, controls
* ASP.NET Framework supports varied languages
Outsourcing author providers furnish unlike services much as the designing and the usage of websites, as advantageously as software and e-commerce development. One big advantage for choosing to outsource your web development needs is you would be competent to get the resource of good engineers to get ample results spell session in your office.
Read More..
Advantages of ASP.NET:
* Any application can talk to a host of other applications, running on diverse technology and hardware, in turn lowering the operation costs. Consider this one case, wherein the stock management system is connected to the accounting system, resulting in ample savings.
* Bring on one platform all your internal applications, your partners as well as your customers.
* Microsoft Visual Studio® .NET and the .NET Framework supports varied languages, in turn helping developers to focus on work at hand instead of trying to learn a new language that can do the job.
* Employees can look for updated information on desktop applications, internet browsers or even mobile devices.
* Optimum speed of development
* Ability of cross platform migration
* High Reliability
* Rigorous Security
* Easy configurations of applications
* Vast and enriched Class library, features, controls
* ASP.NET Framework supports varied languages
Outsourcing author providers furnish unlike services much as the designing and the usage of websites, as advantageously as software and e-commerce development. One big advantage for choosing to outsource your web development needs is you would be competent to get the resource of good engineers to get ample results spell session in your office.
Read More..
Tuesday, November 18, 2008
Windows Azure Tools for Microsoft Visual Studio 2008 SP1
Microsoft has recentky launced the development tool support for Windows Cloud Computing - Windows Azure.
Windows Azure Tools for Microsoft Visual Studio extend Visual Studio to enable the creation, building, debugging, running and packaging of scalable services on Windows Azure.
Windows Azure Tools for Microsoft Visual Studio includes:
*C# and VB Project templates for building Cloud Services
*Integration with the Development Fabric and Development Storage services
*Debugging Cloud Service Roles running in the Development Fabric
*Building and packaging of Cloud Service Packages
*Browsing to the Azure Services Developer Portal
*Role configuration
*SSL Certificate selection
Read More..
Windows Azure Tools for Microsoft Visual Studio extend Visual Studio to enable the creation, building, debugging, running and packaging of scalable services on Windows Azure.
Windows Azure Tools for Microsoft Visual Studio includes:
*C# and VB Project templates for building Cloud Services
*Integration with the Development Fabric and Development Storage services
*Debugging Cloud Service Roles running in the Development Fabric
*Building and packaging of Cloud Service Packages
*Browsing to the Azure Services Developer Portal
*Role configuration
*SSL Certificate selection
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
Uploading In ASP.NET
With classic ASP, uploading a file from the client to a server required one of three approaches: use of a third-party COM component, use of a custom-written component, or (messy) script code. The easiest option providing the most features was to use a third-party COM component, such as SA-FileUp or ASPUpload. Problems with using the COM model for Web application components are numerous. First off, these components must be registered (generally using the regsvr32.exe tool) before they can be used from a conventional ASP application. Remote administration of these types of applications is not possible, because the registration tool must be run locally on the server. These components remain locked on disk once they are loaded by an application, and the entire Web server must be stopped before these components can be replaced or removed. Furthermore, these third-party COM components cost money.
ASP.NET easily allows developers to provide upload support without the need of any COM component. This is accomplished via the HtmlInputFile class in the .NET Framework. An instance of this class can be created and used easily through an ASP.NET Web page in just a few lines of code. In this article we'll examine how to upload a file from the client to the Web server using ths server control. We'll also examine how to add some extra functionality, such as creating the upload directory.
Read More..
ASP.NET easily allows developers to provide upload support without the need of any COM component. This is accomplished via the HtmlInputFile class in the .NET Framework. An instance of this class can be created and used easily through an ASP.NET Web page in just a few lines of code. In this article we'll examine how to upload a file from the client to the Web server using ths server control. We'll also examine how to add some extra functionality, such as creating the upload directory.
Read More..
Tuesday, November 11, 2008
Asp.NET Development Benefits
Microsoft .Net Application Development
Microsoft .NET is a technology that connects information, people, systems and devices. .NET connects a broad range of personal and business technologies, enabling the access and use of important information, whenever and wherever it is needed. Built on XML Web service standards, .NET enables both new and existing applications to connect with software and web application to the services across platforms, applications and programming languages.
Benefits of Asp.net
* Any application can talk to a host of other applications, running on diverse technology and hardware, in turn lowering the operation costs. Consider this one case, wherein the stock management system is connected to the accounting system, resulting in ample savings.
* Bring on one platform all your internal applications, your partners as well as your customers.
* Microsoft Visual Studio® .NET and the .NET Framework supports varied languages, in turn helping developers to focus on work at hand instead of trying to learn a new language that can do the job.
* Employees can look for updated information on desktop applications, internet browsers or even mobile devices.
* Optimum speed of development
* Ability of cross platform migration
* High Class library, features, controls
* ASP.NET Framework supports varied languages
* Reliability
* Easy configurations of applications
* Vast and enriched
Read More..
Microsoft .NET is a technology that connects information, people, systems and devices. .NET connects a broad range of personal and business technologies, enabling the access and use of important information, whenever and wherever it is needed. Built on XML Web service standards, .NET enables both new and existing applications to connect with software and web application to the services across platforms, applications and programming languages.
Benefits of Asp.net
* Any application can talk to a host of other applications, running on diverse technology and hardware, in turn lowering the operation costs. Consider this one case, wherein the stock management system is connected to the accounting system, resulting in ample savings.
* Bring on one platform all your internal applications, your partners as well as your customers.
* Microsoft Visual Studio® .NET and the .NET Framework supports varied languages, in turn helping developers to focus on work at hand instead of trying to learn a new language that can do the job.
* Employees can look for updated information on desktop applications, internet browsers or even mobile devices.
* Optimum speed of development
* Ability of cross platform migration
* High Class library, features, controls
* ASP.NET Framework supports varied languages
* Reliability
* Easy configurations of applications
* Vast and enriched
Read More..
Subscribe to:
Posts (Atom)