VS2017 + Postsharp 5.0.22 prompting to install tools

tankbob4851's Avatar

tankbob4851

20 Apr, 2017 11:15 AM

I keep getting "Do you want to install PostSharp Tools?" every time I compile my project.

I've checked Tools -> Extensions and Update, I have Postsharp tools for Visual Studio 2017 (version 5.0.22) installed.

I know I can click Never ask me again, but surely it shouldn't ask me in the first place?

  1. Support Staff 1 Posted by PostSharp Techn... on 24 Apr, 2017 03:38 PM

    PostSharp Technologies's Avatar

    Hello,

    you are right. It should not ask you if you already have PostSharp Tools for Visual Studio installed.

    Please, Could you zip all %temp%\PostSharp.Settings*.log files and send the archive to us?

    Do you run the build from command line or Visual Studio?

    What version of PostSharp nuget package do you use?

    PostSharp 4.3 compiler cannot see Visual Studio 2017 extensions, so if you use PostSharp 4.3 nuget package, then the question is expected and you can get rid of it, only if you click "Never ask me again".

    -jakub

  2. 2 Posted by Robert Vale on 24 Apr, 2017 04:33 PM

    Robert Vale's Avatar

    Murphy's law, I've just install 5.0.23 and problem has gone away!

  3. Support Staff 3 Posted by PostSharp Techn... on 24 Apr, 2017 04:36 PM

    PostSharp Technologies's Avatar

    Hello,

    We are going to close this request as we believe it was solved. Please feel free to reopen the discussion if you need more help.

    Best regards,

    -jakub

  4. PostSharp Technologies closed this discussion on 24 Apr, 2017 04:36 PM.

  5. tankbob4851 re-opened this discussion on 03 May, 2017 06:14 PM

  6. 4 Posted by tankbob4851 on 03 May, 2017 06:14 PM

    tankbob4851's Avatar

    The problem has now re-appeared.

    This is using postsharp 5.0.23 nugget compiling with visual studio

  7. Support Staff 5 Posted by PostSharp Techn... on 04 May, 2017 09:35 AM

    PostSharp Technologies's Avatar

    Hello,

    we had a look at the logs and they only show that the "Do you want to install compiled images?" is shown to you. I have attached a screenshot of the dialog. Could you please confirm that this is not what you see?

    If it is not, could you please
    1) Send the screenshot of the dialogue you see;
    2) When the dialog is on screen, please use Process Explorer to find the process to which this windows belongs to, as described here: https://superuser.com/a/249416. Then right click on the process (sort alphabetically if the list is jumping), select Properties and send us the command line shown there.

    Thanks in advance for helping us so sort this out.

    Best regards,
    -tony

  8. 6 Posted by tankbob4851 on 04 May, 2017 10:19 AM

    tankbob4851's Avatar

    Nope its the tools dialog

    "C:\ProgramData\PostSharp\5.0.23\bin.Release\PostSharp.Settings.UI.exe" /prepare tools

    Called by
    "C:\ProgramData\PostSharp\5.0.23\bin.Release\postsharp-net40-x86-srv.exe" /tp "postsharp-S-1-5-21-776305611-568246065-4041885241-1177-4.0-x86-release-5.0.23"

    called by
    C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\15.0\Bin\MSBuild.exe /nologo /nodemode:1 /nodeReuse:true

    called by
    "C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\devenv.exe"

  9. Support Staff 7 Posted by PostSharp Techn... on 04 May, 2017 12:07 PM

    PostSharp Technologies's Avatar

    Thanks for the info. We still can't figure out the cause, unfortunately. Could you please rebuild the project with diagnostics verbosity (/v:diag) both from Visual Studio and from command line and send us the console output of MSBuild?

    Best regards,
    -tony

  10. 8 Posted by tankbob4851 on 04 May, 2017 02:40 PM

    tankbob4851's Avatar

    I've attached the detailed log from visual studio,(I was prompted for the tools)

    I haven't been prompted when running the msbuild manually, might need to wait an hour before it reprompts

  11. Support Staff 9 Posted by PostSharp Techn... on 11 May, 2017 09:54 AM

    PostSharp Technologies's Avatar

    Hello,

    thank you for the build log and for the patience with helping us to diagnose this issue.

    It is obvious that some MSBuild properties are not propagated from PostSharp Tools for Visual Studio to MSBuild process but the reason is not clear and we are not able to reproduce such behavior.

    Please, do you have PostSharp Tools for Visual Studio extension enabled in Visual Studio 2017?

    If yes, then the problem might be related to XAML or .NET Standard. Please, do you have any .NET Standard projects/references or XAML files in your solution? Please, do you use project.json?

    The best way how to diagnose and fix issues like this is to have a minimal example project. Please, could you send an example project to us?

    -jakub

  12. 10 Posted by tankbob4851 on 11 May, 2017 10:00 AM

    tankbob4851's Avatar

    Hi,

    Yes I have XAML, I don't have .NET Standard, but what I do have is projects using the .NET standard project format, just targeting .NET 462.

    I'll try and create a dummy project.

  13. 11 Posted by tankbob4851 on 11 May, 2017 10:08 AM

    tankbob4851's Avatar

    Pops the dialog the first time, if I hit cancel, I think I need to wait an hour before it prompts again

  14. Support Staff 12 Posted by PostSharp Techn... on 11 May, 2017 04:07 PM

    PostSharp Technologies's Avatar

    Hello,

    Thank you very much for the example project. We're able to reproduce the issue.

    We're closing the ticket for now as the bug has been internally filed as issue #15035. We will contact you as soon as the bug fix has been released.

    For more details on our support policies and prioritization of bug fixes, please visit https://www.postsharp.net/support/policies

    -jakub

  15. PostSharp Technologies closed this discussion on 11 May, 2017 04:07 PM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac