Re: Compile to GAC from VS

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Hi,

Most of Microsoft Solutions involving Office 2003 use 'Shadow Copying'
(C:\Docuemnt settings\<username>\........). Could I suggest using .NET
Security Policy (CASPOL) to avoid GACing your dlls. I think I use CASPOL and
have never have to delete my Shadow Copy folder to read latest build. The
following might be useful for Office Solution development:
http://msdn2.microsoft.com/en-us/library/zcfbd2sk.aspx

Best regards,

Wamiq
wamiq@xxxxxxx

"Alexander Mueller" <millerax@xxxxxxxxxxx> wrote in message
news:eerTFB4OGHA.344@xxxxxxxxxxxxxxxxxxxxxxx
Michael Höhne schrieb:

I ran into that problem several times. If you do not update the version
number of your assembly, the .NET framework uses a cached assembly in
your C:\Document and Settings\<username>\Lokale Settings\Application
Data\assembly folder. It will be stored somewhere beneath a DL2 or DL3
folder. I placed a simple batch into that folder, removing all assemblies
in there.

@echo off
@prompt $g
del *.dll /s /q
pause

Whenever I have the problems you mentioned, I click it and all assemblies
are gone and you're working with your current implementation. You can add
the batch file to a custom build script to automate this process.

Hi Michael,

thanks very much for your response. It didn't even know this folder
exists. As you proposed, removing the cached dlls actually solves
the problem. Btw, I have no idea how to create a custom built script.
Could you point out, where to integrate a script into the project,
is it under <project-options>-<compile>-<build events>?

Mfg,
Alex


.

Relevant Pages

  • Re: Deploying with Custom References
    ... When loading Assemblies, the Framework uses its own set of rules about where to look and the DefaultLocation folder is one of those places. ... none of the DLLs have entry points, ...
    (microsoft.public.dotnet.languages.vb)
  • Re: deployed website is referencing code-behinds...not the assemblies
    ... because it is referencing the code-behind files and the the DLLs in the ... "the DLLs in the bin folder" ... into the assemblies in bin folder. ...
    (microsoft.public.dotnet.framework)
  • Re: Creating setup project for website
    ... You don't have to use that Project Output option - just pick the individual ... Dlls etc to the Web Application \bin folder. ... single page assemblies is probably required to stop the names changing. ...
    (microsoft.public.vstudio.general)
  • Re: Where can I locate DLLs so other s/w picks them up
    ... > Currently I have just placed these DLLs in the same directory as my ... If you put them in your \bin folder you know ... assemblies in the application configuration file. ... Or you can install the assemblies in the Global Assembly Cache. ...
    (microsoft.public.dotnet.framework)
  • RE: CAS, No Touch Deployment and Flags="UnmanagedCode"
    ... Try using caspol -rsg to figure out what code groups are ... > We No Touch Deploy our assemblies from a web server. ... > On the web server, our assemblies are stored in a folder called, lets say ...
    (microsoft.public.dotnet.security)