Trying to use registration-free com, but there's no Isolated property to turn on???

[sherifffruitfly]

Hi,

Just like the subject says - I'm deploying to users who (apparently)
don't have rights to successfully run regsvr32, so I'm trying to use
the tip found here:

http://msdn.microsoft.com/msdnmag/issues/05/04/RegFreeCOM/default.aspx?print=true&loc=null

As I look at my dll reference in VS, I notice there IS no Isolated
property.

Uh-oh - I just noticed the article is talking about VS2005. I'm using
VS2003, on .NET 1.1 - is registration-free COM not an option for me? If
not, what can I do to get around the user-not-having-regsvr-permissions
issue?

Thanks for any ideas,

cdj

 

[David Browne]

Hi,

Just like the subject says - I'm deploying to users who (apparently)
don't have rights to successfully run regsvr32, so I'm trying to use
the tip found here:

http://msdn.microsoft.com/msdnmag/issues/05/04/RegFreeCOM/default.aspx?print=true&loc=null

As I look at my dll reference in VS, I notice there IS no Isolated
property.

Uh-oh - I just noticed the article is talking about VS2005. I'm using
VS2003, on .NET 1.1 - is registration-free COM not an option for me? If
not, what can I do to get around the user-not-having-regsvr-permissions
issue?

Thanks for any ideas,

The features used on the client to make this work are Windows features, and
have no dependency on VS2005 or .NET 2.0. VS and Click-Once just make it
easy to package up your app correctly. You should be able to create the
manifest by hand and include the COM components in an XCopy deployment of
your app. You might try using VS2005 to create the manifest file and
including (perhaps edited) it in an xcopy deployment of your .NET 1.1 app.

See "Isolated Applications and Side-by-side Assemblies"

"Isolated Applications and Side-by-side Assemblies is a Microsoft Windows
solution that reduces versioning conflicts in Windows-client applications.

With Windows, application developers can build isolated applications that
are fully self-describing and unaffected by changes to the registry, other
applications, or other versions of assemblies running on the system.
Application authors and administrators can use manifests to manage the
sharing of side-by-side assemblies after deployment on either a global or
per-application basis. Customers benefit from isolated applications that are
more stable and more reliably updated."
http://msdn2.microsoft.com/en-us/library/aa375193.aspx

And,

Assembly Manifests
http://msdn2.microsoft.com/en-us/library/aa374219.aspx

David

 

[sherifffruitfly]

You might try using VS2005 to create the manifest file and
including (perhaps edited) it in an xcopy deployment of your .NET 1.1 app.

David

Thanks David - if I had VS2005 available at work, I would try exactly
that

Dagnabit - I just wanted to use ImageMagick to make some on-the-fly
BMPs rather than a full-blown install of GhostScript - lol.

 

[Bobbo]

Dagnabit - I just wanted to use ImageMagick to make some on-the-fly
BMPs rather than a full-blown install of GhostScript - lol.

Take a look at .Net's drawing (GDI+ ?) libraries; you can create
on-the-fly images fairly easily yourself.

 

[sherifffruitfly]

Take a look at .Net's drawing (GDI+ ?) libraries; you can create
on-the-fly images fairly easily yourself.

 

[Atara100]

http://msdn.microsoft.com/msdnmag/issues/05/04/RegFreeCOM/default.asp...

. . . I'm usingVS2003, on .NET 1.1 - is registration-freeCOM not an option for me? . . .

I finally managed to do it (vs2003 + RegFreeCOM). For more details,
look at
http://www.codeproject.com/script/c...46&select=1864931&df=100&fr=467.5#xx1864931xx

Atara