Re: Running a VB.NET Application on a Network Drive

From: Ray (rhartl_at_tscfinancials.com.au)
Date: 06/20/03 

Date: Thu, 19 Jun 2003 18:12:48 -0700

Thanks for the reply. It looks like I am almost there.

There are a couple of questions.

You say you can in Visual Studio, under "general" project
properties st the Wrapper Key File Assembly. I could see
no such options. I must be looking in the wrong place. I
right click on the Project in the Solutions Explorer, and
get a popup window. This shows the Project Properties. On
the left is a tree, I select under Common Properties,
General and see on the right, Assembly Name, Output Type
(Windows Application) etc - but nothing about Wrapper Key
File Assembly. Am I looking in the correct place ? (Help
About shows Microsoft Development Environment Version
7.0.9466, .NET Framework Version 1.0.3705, Microsoft
Visual Basic .NET 55537-640-6669627-18086).

Also what steps do I take to create and apply a .MSI file
if I were to build and deploy this application using
Visual Studio.

Thanks in advance
Ray

>-----Original Message-----
>Hi Ray,
>
>> I have read a lot about Security and .NET and
understand
>> the issue of UNC drives / Intranet etc. The best
approach
>> seems to be to create a "strong name". Will this work?
>
>Yep, that would be the way to go.
>
>> When I compile it now comes up with the error:
>> Unable to emit assembly: Referenced
>> assembly "Interop.Excel" does not have a strong name.
>>
>> I cannot seem to find a way around this. What do I need
>> to do to get around this error?
>
>You can work around this in one of two ways, depending
on if you are using
>Visual Studio or not. If you are generating your COM
interop library with
>tlbimp on the command line, then you can use
the /keyfile parameter to have
>it sign the generated interop libarary. If you are
using Visual Studio,
>then you need to go to your project properties, and
under "general", set the
>Wrapper Assembly Key File to a strong name key.
>
>>
>> Presumably once I get around this, my next steps would
be
>> to add this strong name to my .NET Framework
>> Configuration.
>> This is presumably a matter of adding this Strong
>> Name "power" to the Machine Permission Set with the
>> relevant permissions (eg "FullTrust").
>>
>> My executable would then run on the network drive.
>> Correct?
>
>Correct. If you use the MMC snapin to modify your
security policy, adding a
>new code group will start a wizard that will allow you
to actually pull the
>strong name right off your assembly.
>
>
>>Will running "donetfx.exe" install
>> the .NET Framework?
>
>Yes.
>
>> The other issue in distributing my application on a
>> client PC is how to add the Strong Name to their .NET
>> Framework Configuration. How do I go about automating
the
>> distribution of this? I have read about creating
an .msi
>> file. Is this what I need to do and how to I apply in
on
>> the Client PC.
>
>Creating an MSI would be the easist way to distribute
your modified policy.
>I'm not sure how InstallShield works, so you'll have to
check with them to
>figure out how to run an external MSI package.
>
>-Shawn
>--
>
>--------------------------------------------------
>This posting is provided "AS IS" with no warranties, and
confers no rights
>
>
>.
>

Relevant Pages

  • Re: Common Library .NET and CF.NET
    ... Of course you have to limit your usage of the .NET Framework to the ... share among .NET and .NETCF. ... Visual Studio should define some platform symbol in all Smart ... Both builds can be made from the same source code though. ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: Programming for Electronics Engineers
    ... >> gives you the full power of the .NET Framework. ... >Is that like a cut down version of Visual Studio? ... We're solving math problems, so ... would be learning Linux. ...
    (sci.electronics.design)
  • Re: Opinions on .NET Framework?
    ... I'd like to do some Windows development. ... VS .NET is the only MS development environment at this time. ... there is no Visual Studio .NET anymore. ... support for the .NET Framework without affecting their Visual Studio ...
    (microsoft.public.dotnet.framework)
  • installing outlook com addin
    ... I have created a COM addin to outlook, ... I need to get visual studio .Net to find ... then the final installer can not register my ... a part of the .Net framework, and I do not want to force my users to ...
    (microsoft.public.outlook.program_vba)
  • Re: Visual Studio 2005 Beta 2 project cannot work in IIS virtual d
    ... You need the .Net Framework 2.0. ... Visual Studio 2005 Beta 2 project cannot work in IIS virtual directory ... I used Visual Studio 2005 Beta 2 to build a simple new web site. ... An error occurred during the processing of a configuration ...
    (microsoft.public.dotnet.framework.aspnet)
Loading