Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Remove other DebuggerVisualizers? #44

Closed
fdncred opened this issue May 24, 2018 · 4 comments
Closed

Remove other DebuggerVisualizers? #44

fdncred opened this issue May 24, 2018 · 4 comments
Assignees
@codingadventures
Labels
bug

Comments

@fdncred
Copy link

fdncred commented May 24, 2018

Why does it appear that upon installation via the vsix all my existing .dlls in the Visualizers folder are now deleted?
@codingadventures
Copy link
Owner

Hi, during installation older auto generated visualisers are deleted to avoid errors during data export [PackageConfigurator]

LINQBridgeVs/Src/BridgeVs.VsPackage.Helper/Configuration/PackageConfigurator.cs

Line 274 in c3822ed

private static void DeleteExistingVisualizers(string vsVersion)

However this is clearly a bug, only linqbridgevs autogenerated dlls are to be deleted and not just any dll.

I will fix this in the next release

@codingadventures codingadventures self-assigned this May 24, 2018
@fdncred
Copy link
Author

fdncred commented May 25, 2018

Totally pissed over this. At least you could've moved them to the recycle bin so I could recover them.

@codingadventures
Copy link
Owner

My apologies. I will fix this bug so that it will delete only its own dlls

codingadventures added a commit that referenced this issue May 26, 2018
@codingadventures
#44
d9b216d 
adds filters to delete only linqbridgevs generated dlls in the target visualizer folder
fixes a bug with the error tracking options in the menu
@codingadventures
Copy link
Owner

Fixed in the upcoming release

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@codingadventures codingadventures

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@fdncred @codingadventures