tag:blogger.com,1999:blog-2151936906740408444.post25229091306899185..comments2020-11-24T04:49:32.095-06:00Comments on DotNetizen: Fix : Dll locking issue by Visual StudioRajesh Babuhttp://www.blogger.com/profile/11724949075272660582noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-2151936906740408444.post-39050831975872096262011-01-06T15:04:50.553-06:002011-01-06T15:04:50.553-06:00Sorry to hear that it didnt work out for you, Rite...Sorry to hear that it didnt work out for you, Ritesh. There could be multiple root causes for this kind of issues as you mentioned and thus there may not be a single solution. But having different projects for different types of BizTalk artifacts is ideal pattern used by most. Please provide me with little more information about your environment and I will try to help as much I can. (You know Rajesh Babuhttps://www.blogger.com/profile/11724949075272660582noreply@blogger.comtag:blogger.com,1999:blog-2151936906740408444.post-35225367584331854272010-12-18T17:50:01.061-06:002010-12-18T17:50:01.061-06:00The solution mentioned by you did not work for me....The solution mentioned by you did not work for me. It seems that there is not a signle solution for this. Microsoft agreed that there is problem with BizTalk Server Project template for Visual Studio. They recommend installing 2 hot-fixes, but that still doesn't work. I could not spend much time on this due to time-line and had to alter my solution and used only one project with different Riteshhttps://www.blogger.com/profile/05101041871573554896noreply@blogger.com