381
Views
5
Comments
.Net version for platform server Version 11.16.0 (Build 35766)
Application Type
Reactive
Service Studio Version
11.53.21 (Build 61476)
Platform Version
11.16.0 (Build 35766)

How do I know which version of .NET is running under the hood?

While I'm assuming that Outsystems 11 would typically run 4.7.2+ versions I'm unable to understand why Visual Studio (while creating an extension) says that the project template is that of 4.6.1?

Refer attached screenshot


Screenshot 2022-10-20 130010.png
2023-08-28 07-00-10
Paulo Torres
Champion

Hello,

It seems a question in your extension, if you do the upgrade the message will not appears anymore.

Anyway you can check this link: https://success.outsystems.com/Documentation/How-to_Guides/Integrations/How_to_use_.NET_Standard_libraries_in_OutSystems_extensions

Regards

UserImage.jpg
ARS

Paulo, didn't quite understand your response.


#1 Its a clean slate. No C# code written. I get this message when I initiate the Open in Visual Studio (C#) action from integration studio. 

#2 When I check the project properties on the C# project, it is confirmed that its running 4.6.1

Please share some more insights as to what needs to be upgraded? And yes, there are no additional reference to .NET standard libraries as its a clean slate, just the project template. I'm yet to write any code.

FYI - I'm running VS 2022 Enterprise on a x64 Windows machine

Screenshot 2022-10-20 132825.png
2023-08-28 07-00-10
Paulo Torres
Champion

Hello ARS,

Didn't understood there is no .net code. Anyway you have something inside when you open your extension in visual studio, no?

Did you check this?

UserImage.jpg
ARS

Paulo, what I meant was that I'm starting a fresh extension project. No hand-coding done yet.

From your response, I get that I should just update the target .Net framework and recompile. That should do the job, correct?

However, my question remains that why would it choose 4.6.1 in the first place, especially since I'm running a pretty latest version of the platform + integration studio

2022-03-21 09-36-03
Andy Smy

This question remains unanswered. What .Net framework version should we manually change the target to, which is supported by OutSystems?

You can fix the bug in Integration Studio in your own time if you give us the specific workaround instructions, please.

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.