DotVVM for Visual Studio features

🌎 Discussion in English
1

Hi!

I am currently using the free version of DotVVM for Visual Studio version 4.0.576.0.
In previous versions F12 worked from markup and now doesn’t and I’ve understood that it is no longer available in the free version.
Also, what else seems to not work anymore in version 4.0.576.0 is IntelliSense in markup and error/warning highlight. There are none whatsoever.

Can you confirm if this is intended or not?
I’d like to clarify if I’m having a local issue with the Visual Studio or something else or not.

2

What works and what not:

image
image714Ă—869 43.7 KB

3

Hi!

If we buy the Commercial DotVVM for VS will the error/warning highlighting in markup reappear?
@exyi please help us with a response on this because we have productivity hinderance.

4

I tried to sign out from the extension to simulate the free functionality.

I can see the IntelliSense for DotVVM controls and their properties:

image
image843Ă—185 18.2 KB

image

The IntelliSense in data-bindings does not show as it is the commercial function.
image

The green squiggles are not 100% reliable and sometimes they incorrectly appear in the free version (it is caused by Visual Studio HTML editor that sometimes produces warnings that are not suppressed by the DotVVM extension).
However, validations for usage of DotVVM controls (such as validation of RouteName property in the RouteLink, and so on) do not appear in the free version (it is the Real-time error checking item in the comparison table). They appear in the commercial version.

If you do not have the IntelliSense at all in the free version, that is probably a bug in the extension. Try to run the application so it regenerates the dotvvm_serialized_config.json.tmp file that provides the necessary metadata for the IntelliSense. Also, if there is some errors in the Output window (you have to select the source DotVVM), that would also help us to track the issue.

5

Excuse me, I am referring specifically to bindings in markup:

image
image767Ă—36 3.78 KB

No amount of project cleaning, branch re-checking out, VS restarting, DotVVM extension uninstalling/reinstalling, work station restarting… helped to change it.

I work on VS Version 17.12.3
DotVVM ext:
image

6

I believe that autocompletion in binding is only available in the pro version. Control properties and control names should always work, though.

7

Now you tell me that it is only in Pro (paid version)… :face_with_peeking_eye:
(last month the preview version did have Intellisense in bindings in markup files)
I’m currently setting up the paid version…

8

The Intellisense for bindings in markup files now works in the paid version. Thank you. This is now resolved. :expressionless:

9

image

What does “Preview” mean? We bought it and I’m signed in

10

Sorry, but it has been this way since the dawn of time (DotVVM - Open source MVVM Framework for Web Apps), it is exactly as indicated in your screenshot. I guess it’s possible it worked due to some bugs, it was never intended.

11

:exclamation:

I saw that, yes.

I was confused, the problem was that I forgot or never knew (?) that I was on the paid version of DotVVM extension for VS all along and it expired somewhere in October this year, later falsely believing that the free version changed its behavior and features.

Sorry, my mistake with this entire thread :face_with_open_eyes_and_hand_over_mouth:.