Home › Forums › Discuss Znode Storefront Issues

All sorts of compile problems with VS 2008 and Vista Ultimate 64 and TFS

Jeron's picture
Wed, 05/27/2009 - 20:36 — Jeron

Everything seems to compile fine and run until the solution is put in Microsoft Team Foundation Server, then all sorts of compile errors occur, like...

Could not load file or assembly 'App_Licenses, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The parameter is incorrect. (Exception from HRESULT: 0x80070057 (E_INVALIDARG))

...and...

Cannot copy assembly 'ZNode.Libraries.ECommerce.Catalog.dll' to file 'D:\Projects\Znode Storefront\Enterprise Edition\Web\Bin\ZNode.Libraries.ECommerce.Catalog.dll'. Unable to add 'D:\Projects\Znode Storefront\Enterprise Edition\Libraries\ZNode.Libraries.ECommerce.Catalog\obj\Debug\ZNode.Libraries.ECommerce.Catalog.dll' to the Web site. Unable to add file 'Bin\ZNode.Libraries.ECommerce.Catalog.dll'. The process cannot access the file because it is being used by another process.

... does TFS have some sort of process going that locks DLLs?

Anyone out there using zNode in TFS on a development machine running VS 2008 and Vista Ultimate 64?

‹ IE 8 issues in Admin Quickbooks integration help ›
Thu, 05/28/2009 - 19:33 — GScully
GScully's picture

Uncheck "Enable unmanaged code"

Solution: in the project properties -> Debug option - uncheck the box "Enable Unmanaged Code Debugging"

Thu, 05/28/2009 - 11:46 — rkierner
rkierner's picture

@Jeron, We have several

@Jeron, We have several instances of ZNode source being stored under the TFS Source Control. Much like any source control, you have to be careful not to store the products of a build under source control. Typically these are files in the bin directories. Remove your dlls from the source control library and try to rebuild again.

The key to remember is that you're not building your project in TFS, you're compiling your .cs files that are stored on your file system with the C# Compiler. The only place that TFS could get in the way is marking any files as read-only. Files that are "checked-in" are marked as read-only.

To test this theory, try to "check-out" all the files in the entire solution (from your source control explorer in VS2008). This will mark all the files on your file system as not read-only. Try to build again. If you're still having problems then perhaps you've got another issue going on.

Rick Kierner
HMB (http://www.hmbnet.com)
ZNode Implementation Partner