modelsbuilder / ModelsBuilder.Original

The Community Models Builder for Umbraco
MIT License
114 stars 49 forks source link

Cannot find custom tool on this system #212

Closed owlyowl closed 5 years ago

owlyowl commented 5 years ago

I can verify the extension is installed. I've tried restarting my whole machine.

I've uninstalled and re-installed and it is still not working in vs 2019

zpqrtbnk commented 5 years ago

Hey - did it "solve itself"? or is this still a thing?

owlyowl commented 5 years ago

Hi! Error was between chair and keyboard I was reading your old docs and stumbled upon the new ones with the .mb example

On Tue, Aug 13, 2019 at 7:48 PM Stephan notifications@github.com wrote:

Hey - did it "solve itself"? or is this still a thing?

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/zpqrtbnk/Zbu.ModelsBuilder/issues/212?email_source=notifications&email_token=AAOT4CVZTANRTWGHYQAMHGTQEJ7NRA5CNFSM4ILGKFA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4FEURA#issuecomment-520768068, or mute the thread https://github.com/notifications/unsubscribe-auth/AAOT4CR2N5SDMX5LFM4TPALQEJ7NRANCNFSM4ILGKFAQ .

croban commented 5 years ago

I have same problem with visual studio extension. I am using visual studio 2017 and Umbraco 8.1.4. This are web.config settings for Model Builder:

<add key="Umbraco.ModelsBuilder.ModelsMode" value="Nothing" />
<add key="Umbraco.ModelsBuilder.EnableApi" value="true" />
<add key="Umbraco.ModelsBuilder.LanguageVersion" value="CSharp7" />
<add key="Umbraco.ModelsBuilder.EnableFactory" value="true" />
<add key="Umbraco.ModelsBuilder.ModelsNamespace"  value="Core.Model.PublishedContent" />
<add key="Umbraco.ModelsBuilder.LanguageVersion" value="CSharp7" />
<add key="Umbraco.ModelsBuilder.ModelsDirectory" value="~/../Core/Model/PublishedContent/Generated/" />
<add key="Umbraco.ModelsBuilder.AcceptUnsafeModelsDirectory" value="true" />

Visual Studio Extension is installed and configured: image

image

This happens when "run custom tool" is clicked: image

image

zpqrtbnk commented 5 years ago

Please see this blog post - the custom tool is deprecated and replaced by the extension, which does not work the same

croban commented 5 years ago

That helps thank you!