Do NOT update Visual studio 2019 to 16.3.7

Do NOT update Visual studio 2019 to 16.3.7

Anonymous
Not applicable
1,503 Views
13 Replies
Message 1 of 14

Do NOT update Visual studio 2019 to 16.3.7

Anonymous
Not applicable

After updating visual studio, PSSolid entity can not get all values through the api ( ex. boundingbox)

On my colleague's computer (with VS 16.3.4) the exact same code works perfectly fine.

 

PS: does anyone know how to downgrade VS? 

 

Untitled1.pngUntitled2.png

0 Likes
Accepted solutions (1)
1,504 Views
13 Replies
Replies (13)
Message 2 of 14

Anonymous
Not applicable

Downgrading VS does not work. VS 2017 also doesn't work. 

Just so you know.

0 Likes
Message 3 of 14

luke.edwards.autodesk
Community Manager
Community Manager

I'd suggest it isn't a problem with Visual Studio but more likely a configuration issue within PowerShape.

Do you have PowerShape running with decimal points or commas for the decimal separator?  It should be able to handle both but perhaps that is causing issues.  Is there something different about the PowerShape sessions that you are running?

Luke


Luke Edwards
Consulting Services Manager
0 Likes
Message 4 of 14

Anonymous
Not applicable

Hello Luke, 

I'm using a comma as a decimal separator. This wasn't a issue before the VS update.

Kind regards

 

0 Likes
Message 5 of 14

Anonymous
Not applicable

I'm not quite sure about other settings in PS. How can I check this?

0 Likes
Message 6 of 14

luke.edwards.autodesk
Community Manager
Community Manager

Again, I don't believe it is a Visual Studio issue.

 

Perhaps your computer is running in an strange mixed mode.  Do you have the region of your PC set to a region where the decimal separator is usually a "."?  Try changing your PC config to "." to see what happens.

 

To investigate it more, you could debug the API.  You say this doesn't build on your PC.  What is the error?


Luke Edwards
Consulting Services Manager
0 Likes
Message 7 of 14

Anonymous
Not applicable

Hello Luke,

 

I changed the settings to .  but I still get the same error.

Format is set to Belgium so the standard setting is the , as a decimal separator.

 

"To investigate it more, you could debug the API.  You say this doesn't build on your PC.  What is the error?"

I'm not quite sure what you mean with "this doesn't build on your PC" ?

0 Likes
Message 8 of 14

luke.edwards.autodesk
Community Manager
Community Manager

Sorry, I thought you had said in another post that you were having trouble to clone the source of the API from GitHub and build it.  Have you tried doing this?


Luke Edwards
Consulting Services Manager
0 Likes
Message 9 of 14

Anonymous
Not applicable

I Cloned the API and tried building it, but I get 12 errors.

I'm not quite sure what connection this has with my problem, can you please elaborate?errorlistbuild.png

0 Likes
Message 10 of 14

luke.edwards.autodesk
Community Manager
Community Manager

The missing reference should be here:

C:\Program Files (x86)\Microsoft SDKs\Expression\Blend\.NETFramework\v4.0\Libraries\System.Windows.Interactivity.dll

Perhaps when you installed Visual Studio you didn't choose for "Blend" to be installed?

 

I thought that if you could debug the API you could find out what values PowerShape was giving back and why the API wasn't able to generate a bounding box value from them.

 

You could always disable the WPF projects in Visual Studio as these are not necessary for what you are testing.


Luke Edwards
Consulting Services Manager
0 Likes
Message 11 of 14

Anonymous
Not applicable

Hello Luke,

 

I have it installed but apparently Microsoft made blend or some parts of it opensource, so the places which these are installed changed. I'm not quite sure how it works, so I opened it on VS 2017 and now it only gives 18 warnings.  ( https://devblogs.microsoft.com/dotnet/open-sourcing-xaml-behaviors-for-wpf/)

warnings.png

 

 

How do I disable the wpf projects and how should I test this? (I'm new at debugging the source so I'm not familiar at how this works.)

0 Likes
Message 12 of 14

luke.edwards.autodesk
Community Manager
Community Manager

I've just updated the code on GitHub.  It should now take that reference from NuGet.  If you grab the latest version of the code and build then it should work...  See how you get on with it.


Luke Edwards
Consulting Services Manager
0 Likes
Message 13 of 14

Anonymous
Not applicable

Where can I find documentation how to debug and edit the api? 

I did right mouse click and "build solution" but it doesn't show anything?

0 Likes
Message 14 of 14

luke.edwards.autodesk
Community Manager
Community Manager
Accepted solution

Do you want to PM me and perhaps we can do an online meeting to take a look...


Luke Edwards
Consulting Services Manager
0 Likes