Hi.

When I start Infragistics.AppMap.vsix I just see VS2015.

On VS2015 it's work, but not on VS2017.

François.

Francios,

Please uninstall the AppMapp Extension from both VS 2015, and VS 2017 and then attempt to reinstall the LATEST version from the Marketplace.

After uninstall et reinstall to extension and update tool, 

On VS2017

I can start AppMap without error, but when I what to add contentpage the error "object reference not set to an instace of an object." "Unable to initialize App Map" appear.

VS2015 it's work without error.

Francois.

Francois,

I'm working a version for your that will enable loggings.

In the mean time can you please do the following:

Close all open applications.

Open Windows Explorer and go to your Temp folder:     C:\Users\{YOUR USER NAME}\AppData\Local\Temp

Select all the files and folders and delete them.

Go to: C:\Users\{YOUR USER NAME}\AppData\Local\Microsoft\VisualStudio

You'll then see a folder with a strange name that starts with "15.0_"

Go into that folder.

Then go into the \ComponentModelCache folder

Then delete the files in this folder. (Visual Studio will rebuild this cache on startup)

Restart VS 2017 and see if AppMap works now.  

We have seen issues with the Visual Studio 2017 extensions and updating that corrupts the above cache I asked you to delete.  Rebuilding the cache solves this problem.

Thank you for your time and patience,

Hi Karl,

Thank you very much for you time.

I tried your steps and it did not work.

I completely uninstall Visual Studio professionel 2017 and reinstalled, now everything works well.

I think the probleme occurred after I uninstall Visual Studio Entreprise 2017 RC.

Summary

 - Install VS2017 Entreprise RC (decembre 2016 I think)

- Install VS2017 Professionel (May 3 2017) and AppMap : AppMap work well

 - Uninstall VS2017 Entreprise RC (May 4 2017) : AppMap no longer working on VS2017 Professionel

 - Uninstall VS2017 pro

 - Reinstall VS2017 Pro.

François.

Outstanding.  Have a great day!

No, I did not install AppMap on the RC version, I had installed it on the pro version only.

I uninstall the RC version because I had just installed the pro version.

I believe the problem on pro version occurred after I uninstall the RC version.

Now everything works well.

Francois.