• Replies 2 replies
  • Subscribers 355 subscribers
  • Views 2477 views
  • Users 0 members are here
Options
Related

Building a plugin with Release configuration fails with the error:”Can not access .sdlplugin because it is being used by another process"

Delfina Jovanovska

Building for Release fails with the error:

”The process can not access the file C:\\...\Plugins\Packages\Trados_Plugin.sdlplugin because it is being used by another process"

I’ve cleaned the solution and even the Packages folder in both

AppData->Roaming->SDL->…11

and 

AppData->Local->SDL->…11

I run the “Process Explorer” and it didn’t find any process that was using this file. Please advise.

Thanks!
Rate translation
×
Suggest better translation
×

  • I have realized the same issue...

    Additionally I realized that if you change your output target to ...\AppData\Local\SDL\SDL Trados Studio\11\Plugins\Packages the package creation runs successfully, but the sdlplugin file (and only this file!) is created in ...\AppData\Roaming\SDL\SDL Trados Studio\11\Plugins\Packages too everytime you rebuild your code in AppDataLocal.

    Maybe this helps to find the conflicting access to the sdlplugin file ...

    - Harald
  • in reply to Harald Elsen

    Maybe a workaround that will help ... but only if you have SDL2011SDK installed on your workstation.

    Open the csproj file of your project with a simple text editor (e.g. Notepad++) and goto the following line:

    <Import Project="$(MSBuildExtensionsPath)\SDL\SDLTradosStudio\11\Sdl.Core.PluginFramework.Build.targets" />

    Now change it to

    <Import Project="$(MSBuildExtensionsPath)\SDL\SDLTradosStudio\9\Sdl.Core.PluginFramework.Build.targets" />

    I am sure that this is not recommended, because with this change the build process uses Studio 2011 ressources, but it helps ... Wink

    - Harald

    PS: $(MSBuildExtensionsPath) => "C:\Program Files (x86)\MSBuild"