SharePoint, ASP.NET Relationship

aUnless you've been living under a big rock that you heard of this thing called Microsoft SharePoint. And, like Chicken Little, people in the community of SharePoint is running around saying that the end is near. While there are a lot of power that SharePoint offers it does not mean it will not be written in ASP.NET (define) for longer - on the contrary, SharePoint is a very good behavior ASP.NET 2.0 application itself - - at least in the 3.0/Microsoft Windows SharePoint Services Office SharePoint Server 2007 calendar anyway. That said, there are some differences when it comes to developing with SharePoint that the ASP.NET developer should consider. Here are a few:

Develop on a Server

Most ASP.NET developers are running Windows XP and use construction in IIS to develop your applications. That is the model that most developers are accustomed to. However, SharePoint can not debug remotely so that means developing a Windows Server 2003 or Windows 2003 R2. Of course, most people do not want to run Windows Server 2003 directly on your desktop or laptop. That means that either server virtualization with VMWare or Virtual PC 2007 - which is free. This in turn means more memory than most development teams have. You need at least a gigabyte of RAM for the development of moss and at least 768 megabytes to develop with WSS. Add Windows XP to overheads which actually watching an absolute minimum of 1 GB to do SharePoint development with 2GB of being more realistic, and 3 GB or more of the ideal. Not exactly your standard configuration.

Install

To create in ASP.NET, basically, you install Visual Studio & that is it. Everything is there. Your operating technique already has IIS, & even if you can not use the built in Casini. Unfortunately, nothing comes out of the box with SharePoint - SharePoint even itself. If you need to create WSS have to install WSS. That requires at least three discharges -. NET 3.0 & WSS.
First steps in development becomes more difficult after you install Visual Studio. It is also necessary to install two pieces: Visual Studio extensions for Windows Workflow Foundation (VSeWF) Visual Studio extensions for Windows SharePoint Services (VSeWSS) & Windows SharePoint Services Application Development Kit (SDK WSS). The VSeWF added workflow capabilities of Visual Studio. VSeWSS added some templates (including pieces of cloth & definitions of the list) & solutions of the generators. WSS SDK adds some SharePoint workflow templates specific - in addition to the documentation.