Package class library as wsp for SharePoint Deployment

Matt — Wed, 15 Dec 2010 12:30:57 +0000

Some Visual Studio solutions I’ve come across have class library projects in them. These assemblies have to subsequently be manually copied into the GAC of each SharePoint server. This goes against the standard of using wsp files to deploy assemblies and files into a SharePoint environment. Single servers are easier to manage manually copying assemblies but it’s not a very pleasant way of doing things, move into a multi server environment and you’re in a minefield.
Fortunately there is an easy way to get these assemblies, plus any others you may wish to deploy at the same time, into a wsp. It takes two files and a post build event. Read on..

First up, we need a manifest file. This tells the environment what we would like it to do with the assembly.
Create a new xml file in the root of your project called manifest.xml and add the following code:

xml version="1.0" encoding="utf-8" ?>
<Solution xmlns="http://schemas.microsoft.com/sharepoint/"
  SolutionId="">
  <Assemblies>
    <Assembly Location=".dll" DeploymentTarget="GlobalAssemblyCache">Assembly>
  Assemblies>
Solution>

Replace with a generated GUID and with the name of your dll file.
The DeploymentTarget attribute above specifies that it will be deployed to the GAC, you can use WebApplication if you want it to be deployed to the bin directory of your Webb Application.

You can also specify that the relevant line can be added to the SafeControls section of your web.config file by adding the following inside the Assembly tag above.

<SafeControls>
        <SafeControl Assembly=", Version=1.0.0.0, Culture=neutral, PublicKeyToken=" Namespace="" TypeName="*" Safe="True" />
      SafeControls>

Next up, create a ddf file in the root of your project. I tend to name mine wsp.ddf for consistency. This will contain the instructions on what to package into the wsp file. This file should look like the following.

;Define the output directory and CAB file name (with a wsp extension)
.Set DiskDirectory1="bin\Debug"
.Set CabinetNameTemplate="MySolutionName.wsp"
 
;Include the following files in the CAB Root
manifest.xml
bin\Debug\<assembly>.dll

Now all we have left to do is add a post build event to build the wsp for us.
Go to you project properties (right click project)
Under the Build Events tab under Post-build event command line, enter the following:

:: Change directory to the root of the project
cd "$(ProjectDir)"
 
:: Create a WSP CAB
MakeCAB /f "WSP.DDF"

You can change when the post build event runs, to your liking; normally ‘On successful build’.

That’s it when you have a successful build the wsp file will be generated ready for you to deploy, no more manual copying or editing web.config.

Displaying Crystal Reports in a Web Browser

Matt — Tue, 23 Oct 2007 08:07:26 +0000

Having tried for a while to find the right information for displaying Crystal Reports properly inside a web page using Crystal Report Viewer I finally managed to pull the information together into a solution that works; well for me anyway.

It’s worth mentioning that I don’t use the Crystal Reports extensions for Visual Studio, I have Crystal Server running on the box. I can’t see how this method wouldn’t work through the Visual Studio extensions.

Code Infront

<%@ Register TagPrefix="cr" Namespace="CrystalDecisions.Web" 
Assembly="CrystalDecisions.Web, Version=11.0.3300.0, Culture=neutral, PublicKeyToken=692fbea5521e1304" %>

Place the control where you want it to appear in the page.

<cr:crystalreportviewer id="crReport1" runat="server" hasviewlist="False"
    hastogglegrouptreebutton="False" hassearchbutton="False"
    hasgotopagebutton="False" hasdrillupbutton="False" hascrystallogo="False"
    autodatabind="true" width="350px" displaygrouptree="False"
    height="50px" hyperlinktarget="_blank">

Code Behind

// declare the variables
protected CrystalReportViewer crReport1;
private ReportDocument document1 = new ReportDocument();
private TableLogOnInfos infos1 = new TableLogOnInfos();
private TableLogOnInfo info2 = new TableLogOnInfo();
private ConnectionInfo info1 = new ConnectionInfo();
 
// load the report
document1.Load(Request.PhysicalApplicationPath + "myReport.rpt");
 
// Add the parameters
document1.SetParameterValue("param1", "value1");
document1.SetParameterValue("param2", "value2");
 
//Set the login info for the database
info1.ServerName = ConfigurationSettings.AppSettings["server_name"];
info1.DatabaseName = ConfigurationSettings.AppSettings["database_name"];
info1.UserID = ConfigurationSettings.AppSettings["user_id"];
info1.Password = ConfigurationSettings.AppSettings["password"];
Tables tables1 = document1.Database.Tables;
 
//Apply login info to the report
foreach (CrystalDecisions.CrystalReports.Engine.Table table1 in tables1)
{
    info2 = table1.LogOnInfo;
    info2.ConnectionInfo = info1;
    table1.ApplyLogOnInfo(info2);
}
 
// Bind the report
crReport1.ReportSource = document1;
crReport1.DataBind();

You also need to remember to close the document after it has been rendered to free up memory. This should ideally be done in the Page_Unload method. See this post on MSDN for more information on why it should be placed in Page_Unload.

moopoo.net » Visual Studio

Package class library as wsp for SharePoint Deployment

Displaying Crystal Reports in a Web Browser

Code Infront

Code Behind