Debugging Version Conflict 0.0.0.0 issue about modelsbuilder.original

[zpqrtbnk]

Hey. The error message says "... is not compatible with server version (2.0.3.34)" which means that version 2.0.3-final is properly installed on the server (website) side. The error message says "client version (0.0.0.0) is not..." which is something I don't understand at the moment.

You're not the first one to report that issue. But it makes no sense ;-) Somehow it looks like the extension is corrupted and sends garbage to the site. Any chance you can: open VS2012, uninstall the VSIX extension, close VS2012, re-install the VSIX extension by double-clicking the VSIX file (and making sure you do install for VS2012 and not only VS2013), re-open VS2012 and try again?

[BarryFogarty]

No joy Stephan - still get the same error. I messed around with the tool config, and confirmed if the password is blank, I correctly get a Exception: Invalid configuration. And with an incorrect password, I correctly get a Exception: Response status code does not indicate success (Unauthorized).

With the correct password it is odd as Response status code does not indicate success (Forbidden) would suggest a 403 http error, but maybe that is by design as it is receiving bad config.

As a workaround I was going to try using the dashboard tool, but I don't see a button or anything I can action, is there something I need to do to enable this?

Config: +EnableApi +EnablePublishedContentModelsFactory
Config.ModelsNameSpace: ""

[zpqrtbnk]

The 403 / forbidden error is by design indeed. Client is forbidden to talk to the server because its version is not compatible. Now why is it reporting version "0.0.0.0"?! With the latest 2.0.3-final?! Must debug.

As to how to enable the button... you want to look at that wiki doc page for more details.

[BarryFogarty]

Thanks - I RTFM'd and got the dashboard control working by enabling Zbu.ModelsBuilder.EnableAppCodeModels. That is generating all the models fine so it seems indeed just to do with the VS extension.

Yes I can confirm the latest version custom tool is installed in VS2013 (2.0.3.34)

[zpqrtbnk]

Just to make sure: you seem to mention VS2012 & VS2013... the proper tool is installed on the proper VS, right? (and don't ask me how much time I've wasted debugging the wrong tool on the wrong VS...)

[BarryFogarty]

Sorry, that was a typo, I only use VS2012. I installed the tool from here https://visualstudiogallery.msdn.microsoft.com/3ac3afd4-09db-4c4f-89aa-6ce9e8e7c046

It says it supports both 2012 and 2013 - how do ensure I have installed the proper version?

[zpqrtbnk]

Supports both - it's just that when you install, if VS2012 & VS2013, the installer will display checkboxes for you to pick which VS versions you want to install to. If you're running only VS2012 then it should be fine.

[zpqrtbnk]

Looks like there are issues with JSON serialization of System.Version objects, depending on the version of the serializer, which is difficult to control. Will try to make sure these versions are passed as strings.