Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Jan 12, 2012 04:42 AM by yanamandra
Jan 08, 2012 05:59 PM|LINK
We have migrated all the Projects to VS 2010 (.Net Version 4.0) & TFS 2010.
Earlier Version - VS 2005 (.Net Version 1.1, 2.0) & TFS 2010
Fixed all the build errors that resulted due to the migration and the builds were running correctly when tested in the local environment.Few issues came up which we couldn't anticipate before going with this migration in the server(s).Though we could build the code successfully in the Local environment, when we check-in the code and do the build on the server,
there are no build errors however, we got issues with respect to the Internal Project references.For eg, The main project (WebLayer), which is a Web application refers to many child projects.( eg, BusinessLogicLayer - BLL, DataAccessLayer - DAL).A Project Reference is made from all child projects to the main project.Now, we have made some changes in the BLL and checked-in the changes to server.Did the build, and it was successfully done.Now, TFS dropped the builds to the location specified on the WebServer and when checked for the changes in the UI, the changes were not showing up in the UI.But, the same build when done locally, it's all working as expected.
Then, when we checked the drops, the DLLs are differed in their sizes, and when compared the code between the source DLL
and the DLL which was copied to the Web Project, they do not match. The Dll copied to the Web Layer Project do not have the changes made.The referred project BLL's dll is copied to 2 locations - one to debug folder and another to the _PublishedWebSites\WebLayer\Bin.
Both of them should be same. However, the one copied to Web Project does not have the changes, though the Date Modified is same.
As these drops are all done by TFS itself, we do not have any control on that.As a last resort, we removed the project references and added again, but still it didn't work.At this point of time, we do not have any clue like why it's happening. But, I'm sure, something is missing with respect to the references.
Appreciate any suggestions in this regard.
Thanks and Regards,Srinivas
Jan 12, 2012 04:42 AM|LINK
I could resolve this issue by creating a new catalog for the dlls and pointing all the references to this new catalog.
Hope this will help someone else.