I have never had to deal with this type of issue before and I’m really stuck…
We have a VB .Net program that calls some COM exposed DLLs. I have a series of errors that all point to the same DLL. This is an example of one.
Error 159 'CREATE_TIME' is not a member of 'ImageDataAccess.clsJoinObjDataToObj'. C:\_Team\_Net\_SharedLibraries\ApplicationSpecific\TeamNotesNET\frmAllNotes.vb 1327 32 TeamNotesNET
It is as if the DLL on my machine is pointing at a very old version of ImageDataAccess.
Several members of my team can open the program and build it on their machine without an issue. As best I can tell am pointing at all the same references as them. At this point the only advice left from everyone on my team is to get my machine reimaged. In my environment what that means is a basic image of an IT work station will be loaded onto my machine and I will have to install all the applications I need on it. This will bring my work to a halt for at least a full day. Along with that all my personal setting and the like. It is pretty much the same as getting a new computer.
I’ve checked my references and as I mentioned they seem to be the same as my team mates. The production version software is kept on Tortoise SVN and I have refreshed all that. I went through regedit and deleted all the references to ImageDataAccess. I’ve done everything I can think of.
Can someone get me started on where to look for a solution? I’ll try and answer any questions brought up but in truth my expertise is supporting existing applications with business logic changes and enhancements. I don’t know the nuts and bolts of putting a VB .Net\VB 6.0 com exposed application together and how it all connects.
One other thing is if I connect to the C: drive of one of my team mates who can build the project from my computer and open it up in Visual Studio 2012 I get the same errors.
We have a VB .Net program that calls some COM exposed DLLs. I have a series of errors that all point to the same DLL. This is an example of one.
Error 159 'CREATE_TIME' is not a member of 'ImageDataAccess.clsJoinObjDataToObj'. C:\_Team\_Net\_SharedLibraries\ApplicationSpecific\TeamNotesNET\frmAllNotes.vb 1327 32 TeamNotesNET
It is as if the DLL on my machine is pointing at a very old version of ImageDataAccess.
Several members of my team can open the program and build it on their machine without an issue. As best I can tell am pointing at all the same references as them. At this point the only advice left from everyone on my team is to get my machine reimaged. In my environment what that means is a basic image of an IT work station will be loaded onto my machine and I will have to install all the applications I need on it. This will bring my work to a halt for at least a full day. Along with that all my personal setting and the like. It is pretty much the same as getting a new computer.
I’ve checked my references and as I mentioned they seem to be the same as my team mates. The production version software is kept on Tortoise SVN and I have refreshed all that. I went through regedit and deleted all the references to ImageDataAccess. I’ve done everything I can think of.
Can someone get me started on where to look for a solution? I’ll try and answer any questions brought up but in truth my expertise is supporting existing applications with business logic changes and enhancements. I don’t know the nuts and bolts of putting a VB .Net\VB 6.0 com exposed application together and how it all connects.
One other thing is if I connect to the C: drive of one of my team mates who can build the project from my computer and open it up in Visual Studio 2012 I get the same errors.
