Issues with moving C#.NET project from one machine to another

[StevenK]

We are developing a C#/.NET application. We have on occasions moved our project and source files from one machine to another (from a Windows XP machine to a Windows 2000 machine). On doing so we experience problems.
The first is :
“The dependency ‘Interlop.VBIDE, Version=5.3.0.0, Culture=neutral’ in project ‘Project1’ cannot be copied to the run directory because it would overwrite the reference ‘Interlop.VBIDE, Version=5.0.0.0, Culture=neutral’.”
The second issue is from a file that makes use of Word Documents – I get errors indicating :
“No overload for ‘Open’ takes ‘10’ arguments”
“No overload for ‘SaveAs’ takes ‘11’ arguments”

In addition following a move of a similar project we had an issue with the Crystal Reports that we were using within the Crystal report viewer component in one of the forms.

I can only assume that the reason for the above issues is down to different versions of the DLL’s being made use of (Word, Crystal, etc).
How can we ensure that when we move the project / source files from one development machine to another we maintain the same versions of these included / required / utilised files such that we can build / run the project on any development machine.

Any help / advice would be appreciated.
Thanks in advance.

Steve

 

[OSR]

Is .NET applications portable??? I'm not sure becuase .NET, whatever language you use, uses a bytecode just like JAVA, it's called MSIL. .NET needs this MSIL and of course it doesn't exist on earlier versions of Windows.

Maybe, there is something in your IDE that allows you to compile the program, .NET has JIT. Or maybe check for an update from microsoft that will allow .NET apps to be run on the 2K machine. Rocco is the BOY!!

SHUT YOUR LIPS...

 

[chiph]

My guess is that the IDE installs different assemblies on your computer depending on what operating system you've got installed.

Note that this is a design-time issue, and not a run-time issue -- the assemblies that you produce should run on any machine that has the .NET FCL installed.

My suggestion would be to convert your developer machines to one OS to avoid this code sharing problem.

Chip H.

 

[StevenK]

The suggestion of using a common OS is all well and good but may prove tricky (time consuming, etc.) in this case.
Is there any other suggestions that could be made in this case ?
Thanks again in advance.
Steve

 

[mhauser]

I don't think this is an OS issue. I work with a Win 2000 workstation and the other developers in my group are using XP. Is everyone using the same development environment; are all of you running the same service pack for VS.Net?

 

[sijinjoseph]

The dependency ‘Interlop.VBIDE, Version=5.3.0.0, Culture=neutral’ in project ‘Project1’ cannot be copied to the run directory because it would overwrite the reference ‘Interlop.VBIDE, Version=5.0.0.0, Culture=neutral’.”
The second issue is from a file that makes use of Word Documents – I get errors indicating :
“No overload for ‘Open’ takes ‘10’ arguments”
“No overload for ‘SaveAs’ takes ‘11’ arguments”

This is happening because you have differnet versions of Office installed on the machines.

 

[StevenK]

Does that then mean that every machine I develop / distribute the application to will need to have the same version of Office (or it's consituent parts) ?
I'm hoping that this isn't the case - surely there must be a way of deploying the required files that work with the methods as coded ?
But then this begs the question will these files work comfortably with different versions of the Office applications.
I'm hoping someone has faced these issues and has found the resolution to my problem (and is willing to share it).
Thanks again.
Steve