- This topic has 8 replies, 1 voice, and was last updated 9 years, 2 months ago by
.
-
Posts
-
-
Hi
When I build the solution (4 BizTalk-Projects, each one has some references to others), I got the following error:
Unable to copy file. … Access to the path … is denied.
So I searched in the net for solutions and tried out this:
http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?Feedbac kID=114694
Now I get the following error:
C:\Windows\Microsoft.NET\Framework\v3.5\Microsoft.Common.targets(2606,9): error MSB3021: Unable to copy file “obj\Debug\[assemblyname].dll” to “bin\Debug\\[assemblyname].dll”. The requested operation cannot be performed on a file with a user-mapped section open.
C:\Windows\Microsoft.NET\Framework\v3.5\Microsoft.Common.targets(2606,9): error MSB3021:
Has anyone an idea what could causes these errors?
I already tried to find out if an other process is accessing my files. But its just Visual Studio, who locks the files.
If you have any ideas, please post it.
Kind regards
Daniel
-
Just for information.
My development environment is:
– Windows Server 2008
– BizTalk Server 2009
– Visual Studio 2008
-
Hi,
1. Do yo ureference to Project or to Dll? Tyr to change reference to dll if you use reference to project.
2. Do you use TFS or some another source controlling program? try to open each project which makes you problems and remove “read only” checkbox (it stays thouh undercontrol).
3. Anything interesting in event log?
4. Are you administrator on your machine?
-
Thanks for your answers
@Zx7R: I now tried to change the reference to Dll’s. Now I have some less problems. But still I have in one project this problem.
TFS is not installed. I use Tortoise SVN for source control. It doesn’t lock the file. I allready checked this with process monitor.
The event log doesn’t say anything.
And yes, I am administrator. So it isn’t a permission issue.
I now tried to make for each project a single solution and build one after the other. Result: I was able to build at least the half of the projects.
-
Hi,
May be there a cross reference? You could build and deploy from the beginning?
Look, I have some solution – in my case there are
1. Schemas project it’s a “base” project
2. Maps project – has a reference to schemas’s dll
3. Orchestrations project – has a reference to schemas’ and to maps’ projects dll’sThe base of them is schemas, for deploying it – I delete references from maps and orchestrations, after deploy I add reference of schemas to maps, deploy maps, after it I add reference from Orchestrations to schemas and maps and deploy.
In my case it’s not a problem – cause I don’t add schemas to the project every 5 minutes. Maybe this is a way for you too. Orchestrations could be deployed as many times as I need – without a problem.-
@thanks for all answers
Finally it works. I don’t know exactly why, but now I’m able to build. I changed all referenced first to dll’s and later back to project-references. Now it works. I don’t understand this.
I use the same solution-structure as you have. But to make a final version I like to build all together.
Thanks again
-
-
-
-
-
-
-
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.