Skip to main content

Sharepoint development improvements in Visual Studio 2010

Coding in Sharepoint is not so easy as developers get very minimum support from Visual Studio. For example, if a developer has to make a Web part then he or she has to go to Visual Studio and write down plenty of codes for creating a single control. Manytimes we also use SmartPart right. Hopefully, Microsoft Visual Studio 2010 will offer various features that will make Sharepoint developers' life much more comfortable. I am quickly listing and briefing all those:

  • Web Part Designer: Developer will get designer support for creating web parts. It will work quite similar like the Smart Part but in a better way.
  • Debugging: Debugging Sharepoint applications will be done by "F5". Yeppi, it will be same like any other program in Visual Studio.
  • Sharepoint Server Explorer: All Sharepoint items like lists, document libraries, features and templates will be viewable with in Visual Studio and developers can change and manipulate it directly. Isn't it good guys?
  • WSP Import and Creation: There will be no need to create WSPs manually. Those will be created automatically.
  • Workflow Integration: A new ASP.NET Workflow Initiation Form for the Workflow project will be available with the designer support.
  • Packaging Editor: Package Explorer will be integrated which will support packaging and structuring various Features and WSPs.

    For more information on this, you can visit the following link :
    TechEd EMEA 2008 Keynote, Including SharePoint Tools for VS
  • Comments

    Popular posts from this blog

    Programmatically Playing With SSRS Subscriptions

    SQL Server Reporting Services offers programmatically handling various report subscriptions. You can read the specific subscriptions and change those in code-behind as required. I assume that you are already aware about the subscription mechanism in reporting services. For some of you who are not aware about this, I would like to write that subscription in reporting services is nothing but a automated service (sql server job) defined and set by you to deliver reports at specific time or in specific events. You also define in which format the report will be presented to the user. Now whatever subscription properties you have set, everything will be stored in the ReportServer database. Schedule, Subscriptions and ReportSchedule tables contain alll those informations. Now create a Windows or Web Application. Add a Web Reference towords ReportingService2006. If SSRS is isntalled on your system then you can easily find the ReportService2006.asmx in the following url: http://servername ...

    When ReportServer.resx is gone

    I recieved the following error which I never experienced before in our Sharepoint portal which has SSRS configured in MOSS integrated mode: The resource object with classname "ReportServer" and key "SharedDataSource" was not found. After searching for a while, I found that the ReportServer.resx file was not there inside the App_GlobalResources folder in the virtual directory of the respective portal. I just copied the ReportServer.resx from App_GlobalResources folder under wwwroot and finally pasted it inside the portal's virtual directory. Problem suddenly vanished.

    Some facts on Sharepoint 2010

    By following Lee Richardson's blog , I came to know about few good and few shocking news about Sharepoint 2010. Lets start with some good news: (i) Sharepoint 2010 will have inline list editing with AJAX Support. (ii) Workflows created using Sharepoint designer can be resued by the same way what Visual Studio does (iii) Sharepoint 2010 will support ASP.NET Data Services API. (iv) BDC will also insert or update the data. (v) You can edit Sharepoint Solutions without touching XML! Whooo!!! To me, shocking news is related to the requirement part: (i) Windows Server 2008 will be needed. So what will happen to me if I have Windows 2003? (ii) 64 bit SQL Server 2005/2008 is needed. (iii) There will be no support for Sharepoint 2010 in IE6. I am not sure whether it is because of AJAX or not.