13

3

I downloaded and installed the lastest FogBugz add-in for Visual Studio. I am running Visual Studio 2010 Ultimate. When I click on "View >> Other Windows >> FogBugz" nothing happens. No window, no errors. I have uninstalled and re-installed multiple times. Any ideas out there as to how to debug this problem or better yet a solution?

John

flag

3 Answers

8

I just had that, took me a while to figure out...

Start VS using admin privileges (i.e. Right clicke -> Run as Administrator). Then go to Tools -> Add-In Manager. There, you can click Startup in the Fogbugz line, to enable it.

Next time you start VS, even not in admin mode, you should have it still there.

I think that is caused because its an Addin and not an Extension - though I'm not sure what the difference is.

link|flag
I'm having the same problem as the OP and I've tried your solution but it's not working as expected. When I run VS 2010 as admin the FogBugz window opens right up, but it doesn't otherwise even though it is set to start when VS loads. The add-on is currently installed in My Docs instead of program files, but that didn't help either. Any ideas? Thanks!! – evan Jun 23 2011 at 20:59
@evan - really dont know. Do you get any error messages? Are there file permission restrictions? – Avi D Jun 30 2011 at 21:17
@Avi D - No, I'm not getting any error messages. The fogbugz window just doesn't open on startup and can't be opened via view->other windows unless I run VS in admin mode. As you suggest, it most likely is some kind of file permission problem but I have no idea which files. I've made sure that the entire fogbugz install directory is owned by my me and that have full permissions (used takeown and icacls commands and installed the add-in in both my docs and the default program files). Any idea what other file could have permission problems? Thanks for your help! – evan Aug 27 2011 at 22:26
@Avi D - Also in case it's related I'm running VS 2010 with SP1 on Win 7 x64. Thanks again! – evan Aug 27 2011 at 22:27
I'm getting the same issue as @evan. Any luck? – waynewerner Nov 23 2011 at 17:07
1

I had the exact same problem, and after a few emails with fogcreek support, what solved the issue for me is to follow the instructions in that blog post

http://blog.tabsstudio.com/2010/04/20/missing-stdole-dll-with-a-custom-visual-studio-2010-installation/

Basically it happens 'If you perform a custom Visual Studio 2010 installation selecting only C++ development tools on a clean Windows 7 x64 machine'

Haha what are the odds ? HTH

link|flag
0

Update: It appears that my problem was caused by still having the old SourceLinks/FogBugz bundle installed. I uninstalled both, rebooted for good measure, then re-installed the latest FogBugz add-on.

The FogBugz window still didn't show up when I started Visual Studio so I opened it as Administrator, confirmed that the FogBugz window was displaying, looked at the Add-on settings, etc. (Note: I made no changes) and then restarted VS as my normal user - where the FogBugz window appeared and I was able to connect to our server.

Original:

I was having the same issue as the OP, with the same setup as @Avi D. I tried the answer suggested by @Avi D and now I'm getting the following error when Visual Studio starts up:

Problem signature: Problem Event Name: CLR20r3 Problem Signature 01: devenv.exe Problem Signature 02: 10.0.40219.1 Problem Signature 03: 4d5f2a73 Problem Signature 04: mscorlib Problem Signature 05: 4.0.0.0 Problem Signature 06: 4e181ae3 Problem Signature 07: 3789 Problem Signature 08: 3e Problem Signature 09: System.UnauthorizedAccess OS Version: 6.1.7601.2.1.0.256.1 Locale ID: 1033

Additional information about the problem: LCID: 1033

link|flag

Your Answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.