after updating to the new beta release I get the following errors when I try and use debug or monitor the serial port.

Visual micro was unable to load a debugger extension.
Assembly C:\Program Files (x86)\Visual Micro\Visual Micro for Arduino\Micro Exetensions\Debugger Visualations\PerformanceMonitor\bin/PerformanceMonitor.dll
Type: VisualizationExamples.PerformanceMonitorWindow
Exception has been thrown by the target of invocation

and then

Unable to load debugger visualization C:\Program Files (x86)\Visual Micro\Visual Micro for Arduino\Micro Exetensions\Debugger Visualations\PerformanceMonitor\bin/PerformanceMonitor.dll
Exception has been thrown by the target of an invocation

I have tried uninstalling and re installing a few times now

I typed the error messages out myself.. spelling errors are on me..

yes I downloaded the new new msi's after installing the new msi's that had issues last week.

I will try and reinstall everything again for a 5th time..

I re installed vm + debug again..

I am on windows 7 so .net 3.5 sp1 is built in, I verified it was installed though.

used this tool

http://blogs.msdn.com/b/astebner/archive/2008/10/13/8999004.aspx



still getting errors when I run any of the reporting tools.
Report Analogs
Report Digitals
Report Free Memory

or use {@ReportFreeMemory} in a break point.


any other ideas?

visual micro debugger data extensions was in the assembly folder

I had two versions though.. version 1.0 and 3.5

I deleted version 1 and it made no change..

debug upgrade was installed as admin.



opening the performance monitor window throws these errors 
===
Warning      1      Could not find type 'VisualizationExamples.PerformanceMonitorControl'.  Please make sure that the assembly that contains this type is referenced.  If this type is a part of your development project, make sure that the project has been successfully built using settings for your current platform or Any CPU.            0

Warning      2      The variable 'memoryUsageGraph' is either undeclared or was never assigned.      C:\Program Files (x86)\Visual Micro\Visual Micro for Arduino\Micro Extensions\Debugger Visualizations\PerformanceMonitor\PerformanceMonitorWindow.Designer.cs      48

Warning      3      The referenced component 'ZedGraph' could not be found. 
===

opening the performance monitor control throws these errors
===
Could not find type 'ZedGraph.ZedGraphControl'. Please make sure that the assembly that contains this type is referenced. If this type is a part of your development project, make sure that the project has been successfully built using settings for your current platform or Any CPU. 

The variable 'zg1' is either undeclared or was never assigned. 

===

I am a novice when it comes to VS 2010, maybe I am missing an add in?

also still waiting for you to confirm that you have a "Micro Extensions" folder below the visual micro program folder? It's very important

can you please zip up your vm folder and all sub folders and email to info [at] visualmicro.com

if they look okay then I'll have to see if I can make a build with better error messages and also some trace messages so we can what is going on.

I guess you have checked that this path matches where the performance monitor is located? Sorry if stupid question

C:\Program Files (x86)\Visual Micro\Visual Micro for Arduino\Micro Extensions\Debugger Visualizations\PerformanceMonitor\bin\PerformanceMonitor.dll

Got it thanks. Install looks perfect 

Vs is failing to load the visualizations. The way they are loaded VS is passed the dll name and the name of the class which is defined in each MicroExtension.xml file in each visualization control source folder.

Visual Micro doesn't have any control over this process other than supplying vs with these two pieces of information.

VS requires that each visualization control is built as a COM Visible windows control. All of the Visualizations are COM Visible and we know this is true because they work for everyone else who I know is using them.

A COM Visible control is a control that support windows OLE automation.

So I can currently only see two possible reasons for this problem. 1) the location of the dll is wrong or 2) the visualization dlls are not self-registering as OLE objects in your windows registry 

We know that 1) is correct because you have confirmed the dll path matches the path shown in the vs errors. So it must be 2) I guess.

As a thought, have you tried running vs as administrator. Maybe it's a permissions error with the ole registration? If the controls load okay after running vs as admin you should be able to run vs normally.

If this doesn't work then I will send you the source of a very basic visual studio addin project that attempts to load one control. Running the project in debug mode and will probably give a more informative error message. This will take a few days before I have time so hopefully admin mode fixes it.

Great news. This is what a beta is for. It will happen to others but thanks to you I know where to suggest users look for a solution

Sandro,

This thread is resolved. Please open a new thread if you have a problem. Thanks