I have had a similar problem when using the XSL debugger to transform XML
process does not release the assembly. The size of the XML file I've used to
reproduce this problem is 284 KB. Using Process Explorer, I've seen that it
This post prompted me to report this as a bug. If you have any insight, I'd
""Gary Chang[MSFT]"" <v-garych@online.microsoft.com> wrote in message
news:GsAemzhJGHA.3680@TK2MSFTNGXA02.phx.gbl...
> Hi Mark,
>
>>Can anyone explain to me why VS2003 is suddenly
>>(as in, "this didn't used to happen!!!!!!!!!") having a problem
>>copying an assembly it's building to the runtime directory?
>>...
>
> If you mean this problem only happens to your
> 'OlbertMcHughLLC.DBFramework.MetaData.dll' assembly, I think it may be
> caused by one of the following conditions:
>
> 1. The assemblies that you compile is larger than 64 kilobytes (KB) or
> 2. The corrsponding solution contains projects that are compiled to the
> same output folder or
> 3. The Copy Local property on one of the referenced assemblies or projects
> is set to False.
>
> To work around such problem, you can do any (or all) of the following, as
> appropriate for your projects:
>
> 1. Compile the outputs for individual projects to different folders.
> Visual
> Studio .NET 2003 do not support a common output folder.
> 2. Set the Copy Local property for the referenced assembly or project to
> True.
> 3. Verify that you do not have the Object Browser window open.
> 4. Verify that you do not have the same project (or projects) open in
> another instance of Visual Studio .NET.
>
> Please refer to the following KB article for the details:
>
> BUG: "Could not copy temporary files to the output directory" error
> message
> when you build a solution that contains multiple projects
>
http://support.microsoft.com/default.aspx?scid=kb;en-us;313512 >
>
> Thanks!
>
> Best regards,
>
> Gary Chang
> Microsoft Community Support
>
> ======================================================
> PLEASE NOTE the newsgroup SECURE CODE and PASSWORD will be updated at 9:00
> AM PST, February 14, 2006. Please complete a re-registration process by
> entering the secure code mmpng2006 when prompted. Once you have entered
> the
> secure code mmpng2006, you will be able to update your profile and access
> the partner newsgroups.
> ======================================================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from this issue.
> ======================================================
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> ======================================================
>