SQL Packager and Visual Studio 2008 - ZLib -object reference

le001ya

When upgrade SQL Packager C# project to Visual Stuido 2008, Zlib raised the following error. Any help is greatly appreciated.

Event Type: Error
Event Type: Error
Event Source: ConquestPPD
Event Category: None
Event ID: 0
Date: 8/4/2008
Time: 1:58:18 PM
User: N/A
Computer: MNXPAPPSSSBUILD
Description:
Object reference not set to an instance of an object.
at RedGate.Compression.ZLib.CompressionStream..ctor(Stream stream, Boolean writeable, Int32 chunkSize)
at RedGate.Compression.ZLib.CompressionStream..ctor(Stream stream, Boolean writeable)
at Package.ConquestPPD.PackageResourceManager.DllHandlerFront.GetBatchCount(Int32 fileIndex)
at Package.ConquestPPD.PackageResourceManager.SQLBatches.SQLBatchesEnumerator.MoveNext()
at Package.ConquestPPD.PackageExecutor.ExecutePackage()
at Package.ConquestPPD.PackageExecutor.Execute()
at Package.ConquestPPD.PackageApplication.ExecutePackageQuietly()

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

le001ya

This issue was reported by someone else by the title

object reference not set to an instance of an objec
Mon Mar 10, 2008 4:30 pm

Is this a bug? Did it get fixed in the latest 5.5 version?

Thanks.[/quote]

Brian Donahue

Hi,

I can't check against this at the moment, but historically, you cannot upgrade SQL Packager projects to newer versions of .NET Framework because MS always seem to change the .resx format that the SQL resources use so that it is no longer compatible. If the SQL Packager project is compatible with .NET 2.0, it should probably only be edited using VS2005.

Brian Donahue

Hi,

You may also want to let us know if you are compiling the project as 64-bit. The zlib.dll resource that comes in the package is a 32-bit version and can't be linked from a 64-bit application.

le001ya

Is the new SQL Packager 5.5 generate C# code in VS 2008 format? and does it support 64-bit?

My company has SQL Packager 5.0, and it generates C# code in Visual Studio 2003. The C# project in VS 2003 upgrade to VS 2005 work fine. But the same C# project in VS 2003 upgrade to VS 2008 did not work.

The work around is to compile the C# project in VS 2005.

Currently, our application only support 32-bit. We intend to support 64-bit soon.

Tom Harris

SQL Packager 5.5 generates VS2005 projects. However, you can openand convert them in VS2008. I have done this succesfully on a 32bit machine and executed the resulting package without error.

SQL Packager 5.5 also works on x64 now.

Thanks, Tom

Tom Harris - Red Gate Software