|
Exception |
Post Reply 
|
| Author |
 Share Topic Printable Version Delicious Digg Facebook Furl Google Boomarks Google Buzz MySpace Newsvine reddit StumbleUpon Translate Twitter Windows Live Yahoo Bookmarks Topic Search  Topic Options
|
davidklitzke 
IdeaBlade 
Joined: 14-Jun-2007 Posts: 715 |
 Post Options
 Quote Reply
 Topic: ExceptionPosted: 02-Nov-2007 at 11:16am |
|
The ORM AddIn should not normally appear in both C:\Users\<user>\AppData\Roaming\Microsoft\MSEnvShared\Addins and C:\Users\All Users\Microsoft\MSEnvShared\AddIns. Instead, it normally appears only in the C:\ProgData\Microsoft\MSEnvShared\AddIns folder (as it does on my system). The InstallShield installation targets the AddIn for the [CommonAppData] folder, and I suspect that the reason for these different mapping behaviors is due to different versions of Vista. Different hardware systems can also make a difference. For example, we had a bug that we fixed this summer that only occurred on VAIO laptops. I noticed that you wondered why DevForce installs files into the All Users folder even though you specified you wanted the installation to occur for yourself only. The answer is that DevForce really does not implement a great "for me only" installation. For example, we always install into the machine-wide "Program Files" directory. and the intended target folder for the ORM AddIn is an "All Users" or "ProgData" subfolder.
You also commented earlier that the "Object Mapper Installer" doesn't work. We agree and it has been removed from our current 3.5.5.1 version. On the other hand, the Troubleshooting section for failed Object Mapper installation has been greatly improved.
Edited by davidklitzke - 02-Nov-2007 at 11:17am |
|
 |
|
|
Linguinut
Senior Member 
Joined: 14-Jun-2007 Location: United States Posts: 394 |
Post Options
Quote Reply
Posted: 02-Nov-2007 at 10:23am |
|
Super! Glad to hear you got it working. Vista is nice, though a bit quirky.
Have a great weekend!!
Bill
|
|
|
|
|
pinki
Newbie 
Joined: 02-Nov-2007 Posts: 7 |
Post Options
Quote Reply
Posted: 02-Nov-2007 at 10:21am |
|
It works. The dll was not in the path:
C:\Users\<user>\AppData\Roaming\Microsoft\MSEnvShared\Addins
Just the addin - File
I don't know why the dll was missing, but it works now.
By the way: Why is the addin installed in
C:\Users\<user>\AppData\Roaming\Microsoft\MSEnvShared\Addins
and
C:\Users\All Users\Microsoft\MSEnvShared\AddIns
I have just a user installation.
|
|
|
|
|
pinki
Newbie
Joined: 02-Nov-2007 Posts: 7 |
Post Options
Quote Reply
Posted: 02-Nov-2007 at 10:10am |
|
Yes I have admin rights. It is a vista system, so you never know :-) I start visual studio as admin. (run as admin) which I think is very ugly, but as I read in another thread this is (unfortunately) nessessary for the object mapper add-in. got knows why.
|
|
|
|
|
pinki
Newbie
Joined: 02-Nov-2007 Posts: 7 |
Post Options
Quote Reply
Posted: 02-Nov-2007 at 10:08am |
|
yes I have uninstalled and reinstalled several times. I haven't reinstalled visual studio though but I won't do that! I read that in another thread when the add-in is not shown in the add-in manager, but that's not the case here.
|
|
|
|
|
pinki
Newbie
Joined: 02-Nov-2007 Posts: 7 |
Post Options
Quote Reply
Posted: 02-Nov-2007 at 10:05am |
|
No! I am installing the Version 3.5.4. I just copied the string from the wrong installation package but I have checked the version. Would you please not close the forum before I have confirmed that I have fixed the bug!
|
|
|
|
|
Linguinut
Senior Member
Joined: 14-Jun-2007 Location: United States Posts: 394 |
Post Options
Quote Reply
Posted: 02-Nov-2007 at 10:03am |
|
Another thought...do you have admin rights on the workstation?
[Edit] Just checking the bases...running through what I would do when up against an unusual error. Edited by Linguinut - 02-Nov-2007 at 10:04am |
|
|
|
|
Linguinut
Senior Member
Joined: 14-Jun-2007 Location: United States Posts: 394 |
Post Options
Quote Reply
Posted: 02-Nov-2007 at 10:02am |
|
Have you tried the Uninstall/DeleteAllTempFiles/Reinstall route?
|
|
|
|
|
pinki
Newbie
Joined: 02-Nov-2007 Posts: 7 |
Post Options
Quote Reply
Posted: 02-Nov-2007 at 9:53am |
|
Sorry, I posted the wrong version. I installed Version 3.5.4
|
|
|
|
|
pinki
Newbie
Joined: 02-Nov-2007 Posts: 7 |
Post Options
Quote Reply
Posted: 02-Nov-2007 at 9:53am |
|
Yes, I've looked at that thread, but I get a different error message. Could that still be related?
|
|
|
|
|
davidklitzke
IdeaBlade
Joined: 14-Jun-2007 Posts: 715 |
Post Options
Quote Reply
Posted: 02-Nov-2007 at 9:27am |
|
It looks to me that you are trying to install a very old release of DevForce. In particular, this looks like the DevForce 3.1.0.2 version that we released in early February of last year. DevForce 3.1.0.2 did not support Vista.
Please get the free upgrade from our download site.
|
|
|
|
|
Linguinut
Senior Member
Joined: 14-Jun-2007 Location: United States Posts: 394 |
Post Options
Quote Reply
Posted: 02-Nov-2007 at 9:09am |
|
Have you looked at this thread? http://www.ideablade.com/forum/forum_posts.asp?TID=25&KW=vista, it might help.
Bill
|
|
|
|
|
pinki
Newbie
Joined: 02-Nov-2007 Posts: 7 |
Post Options
Quote Reply
Posted: 02-Nov-2007 at 2:59am |
|
I have installed DevForce Version DevForce.060213.3102.setup on Vista and when I try to activate the object mapper tool in visual studio professional I get the following exception:
Any Idea: The Object mapper installer fails (as always in all previous versions and all devforce version I have installed on all systems I have seen by the way)
 |
|
|
|
|
Post Reply
|
| Forum Jump | Forum Permissions You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |