GzipStream Limitation - does VS2005/2008 include J# classes?

[Rich P]

I have a compression app in VS2003 which uses

using java.util;
using java.util.zip;

and can manipulate files from winzip and other such utilities.

I also have a compression app in VS2005 which uses

using System.IO;
using System.IO.Compression;

which contains GZipStream, but can't work with zip files created in
winzip. I tried adding

using java.util;
using java.util.zip;

in my VS2005 app, but got compilation errors. Does VS2005/2008 install
contain J# classes? If so do I have to load them manually?

Is there a workaround the for GzipStream limitation without needing a
3rd party zipping class -- something equivalent to the J# classes in
VS2003?

Thanks,

Rich

 

[Peter Duniho]

[...] I tried adding

using java.util;
using java.util.zip;

in my VS2005 app, but got compilation errors. Does VS2005/2008 install
contain J# classes? If so do I have to load them manually?

Your project won't even be able to use regular .NET classes unless you add
the necessary references to the project. The "using" directive is
strictly a convenience; it has nothing to do with what libraries are
actually referenced during compilation. See "Add Reference..." in the
project menu.

That said, I don't see any evidence on MSDN that ZipInputStream or related
classes are actually part of the .NET framework. All the documentation
seems to be from VS6. So I can't tell you what assembly you would need to
add as a reference, assuming it's supported at all. But if and when you
find the necessary assembly, you'll need to add it as a reference to your
project in order to use the classes in that assembly.

Pete

 

[Rich P]

Thank you very much. It turned out to be a reference issue:

vjslib

which is located in the framework2.0 folder. So I guess it comes with
VS.

Now I have a compression app in VS2005 which can work with winzip using
some J# classes.

Rich