Posts

Showing posts from April, 2009

How to Create & Deploy Stored Procedure from C# [CLR 3.5]

Image
It was really tough to go back and forth between Visual Studio and SQL management Studio to create and reference back stored procedures. And, you have to have the SQL skill set to create SQL scripts at the Back End. But, it has become simpler now a days. Microsoft came up with a new project type to create SQL database projects right inside Visual Studio 2008. Follow the same .NET syntaxes while creating a Data Connection/Data Commands/Data Readers etc. I will briefly walk through the process: 1. Create a SQL Server Project in C# 2. Select the Database Reference 3. Add a Stored Procedure Class 4. Write the Stored Procedure Like This: using System; using System.Data; using System.Data.SqlClient; using System.Data.SqlTypes; using Microsoft.SqlServer.Server; public partial class StoredProcedures { [Microsoft.SqlServer.Server.SqlProcedure] public static void MySP1(string _UNID) { try { SqlConnection conn = new SqlConnection(); conn.Connect

Create your First Silverlight Application using LINQ and Web Services

Image
Create your First Silver light Application using LINQ and Web Services 1. Create a New Silverlight Application project and name it “ImageViewer” 2. Select ASP .NET Web Application Project and change the name for the web project to “ImageViewer_Web” 3. The solution includes two projects. One is for the Silverlight Control [i.e. ImageViewer] and Another one is for the ASP .NET web system [i.e ImageViewer_Web] 4. Now, we have to create a data context using LINQ to SQL features in ImageViewer_Web project. To do that, right click on the Web Project and Select Add->New Item and Select LINQ to SQL Classes 5. Then Open Server Explorer (View->Server Explorer). Create a connection to the “ImageViewer” database and drag and drop the Tables (tblIndex, DocType, tblDoc) into the left pane and Stored Procedures (getDocuments(), getDocumentTypes()) into the right pane of ImgDataManager.dbml 6. Name the data context as “ImgDataManagerDataContext” and set Serialization mode to Unidirectional 7. If

Developing Business Process and Integration Solutions Using Microsoft BizTalk Server 2006

Windows Workflow Foundation - ORCAS

Visual Source Safe to SharePoint Transformation By Keeping VSS Version History

VSSImporter is a windows based application to bring the Source Safe Documents into the SharePoint List. This application also keeps track of VSS versions and uploads them as a SharePoint version file. But, we have to turn the SharePoint versioning ON to bring the VSS versions into SharePoint. We should be able to run this application in 32 bit platform. Because, VSS is a 32 bit application where as SharePoint supports 32 bit as well as 64 bit. So, we cannot reference VSS and SharePoint DLLs with different platform settings i.e. 64 bit. Otherwise, you might get the following errors: 1. If 64 Bit Platform Settings is Used in Visual Studio we will get the following error from Interop.SourceSafeTypeLib.DLL or ssapi.dll Retrieving the COM class factory for component with CLSID {783CD 4E4-9D54-11CF-B8EE-00608CC9A71F} failed due to the following error: 80040154. 2. If 32 Bit Platform Settings is Used in Visual Studio to reference 64 Bit SharePoint we may get the following error from Microsoft

Visual Studio 2008 Presentation