.NET Portability Analyzer doesn't match .NET API Browser results
I have a conflicting results between the .NET Portability Analyzer (VS extension) and the official .NET API Browser: https://docs.microsoft.com/en-us/dotnet/api
When analyzing a .NET Framework assembly with the portability analyzer, I have the following result for the type System.Security.Permissions.FileIOPermissionAccess:
This would suggest that the type is only available in the upcoming 3.0 release of .NET Core. However when using the aforementioned API browser, it clearly states that the type is already available in version .NET Core version 2.0.
I prefer to trust the API browser, but I just wondered if anyone had a different interpretation of the output given by the portability analyzer.
.net .net-core
asked Nov 20 '18 at 10:28
Mr DaviesMr Davies
1249
add a comment |
I have a conflicting results between the .NET Portability Analyzer (VS extension) and the official .NET API Browser: https://docs.microsoft.com/en-us/dotnet/api
When analyzing a .NET Framework assembly with the portability analyzer, I have the following result for the type System.Security.Permissions.FileIOPermissionAccess:
This would suggest that the type is only available in the upcoming 3.0 release of .NET Core. However when using the aforementioned API browser, it clearly states that the type is already available in version .NET Core version 2.0.
I prefer to trust the API browser, but I just wondered if anyone had a different interpretation of the output given by the portability analyzer.
.net .net-core
asked Nov 20 '18 at 10:28
Mr DaviesMr Davies
1249
add a comment |
I have a conflicting results between the .NET Portability Analyzer (VS extension) and the official .NET API Browser: https://docs.microsoft.com/en-us/dotnet/api
When analyzing a .NET Framework assembly with the portability analyzer, I have the following result for the type System.Security.Permissions.FileIOPermissionAccess:
This would suggest that the type is only available in the upcoming 3.0 release of .NET Core. However when using the aforementioned API browser, it clearly states that the type is already available in version .NET Core version 2.0.
I prefer to trust the API browser, but I just wondered if anyone had a different interpretation of the output given by the portability analyzer.
.net .net-core
asked Nov 20 '18 at 10:28
Mr DaviesMr Davies
1249
I have a conflicting results between the .NET Portability Analyzer (VS extension) and the official .NET API Browser: https://docs.microsoft.com/en-us/dotnet/api
When analyzing a .NET Framework assembly with the portability analyzer, I have the following result for the type System.Security.Permissions.FileIOPermissionAccess:
This would suggest that the type is only available in the upcoming 3.0 release of .NET Core. However when using the aforementioned API browser, it clearly states that the type is already available in version .NET Core version 2.0.
I prefer to trust the API browser, but I just wondered if anyone had a different interpretation of the output given by the portability analyzer.
.net .net-core
.net .net-core
asked Nov 20 '18 at 10:28
Mr DaviesMr Davies
1249
asked Nov 20 '18 at 10:28
Mr DaviesMr Davies
1249
asked Nov 20 '18 at 10:28
Mr DaviesMr Davies
1249
asked Nov 20 '18 at 10:28
Mr DaviesMr Davies
1249
asked Nov 20 '18 at 10:28
Mr DaviesMr Davies
1249
1249
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
This is a bit tricky. The type will be part of .NET Core 3.0, it does not ship as part of .NET Core 2.0 or 2.1, but is available via an additional NuGet package (System.Security.Permissions).
The tools and documentation may have a different view on what is "part of" a particular version of .NET Core and what is "usable" in some way on a particular version.
An additional source you can check is apisof.net: https://apisof.net/catalog/System.Security.Permissions.FileIOPermissionAccess
which correctly lists the type as .NET Core 3.0 and ".NET Core + Platform Extensions" 2.0 and 2.1
answered Nov 20 '18 at 11:04
Martin UllrichMartin Ullrich
45.7k7124126
Ok I understand now. Indeed, I found in the analyzer settings the options ".NET Core/Standard + Platform Extensions". When checked, the resultant column is consistent with the results found with the API Browser. Thanks also for the additional resource.
– Mr Davies
Nov 20 '18 at 11:24
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53390956%2fnet-portability-analyzer-doesnt-match-net-api-browser-results%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
This is a bit tricky. The type will be part of .NET Core 3.0, it does not ship as part of .NET Core 2.0 or 2.1, but is available via an additional NuGet package (System.Security.Permissions).
The tools and documentation may have a different view on what is "part of" a particular version of .NET Core and what is "usable" in some way on a particular version.
An additional source you can check is apisof.net: https://apisof.net/catalog/System.Security.Permissions.FileIOPermissionAccess
which correctly lists the type as .NET Core 3.0 and ".NET Core + Platform Extensions" 2.0 and 2.1
answered Nov 20 '18 at 11:04
Martin UllrichMartin Ullrich
45.7k7124126
Ok I understand now. Indeed, I found in the analyzer settings the options ".NET Core/Standard + Platform Extensions". When checked, the resultant column is consistent with the results found with the API Browser. Thanks also for the additional resource.
– Mr Davies
Nov 20 '18 at 11:24
add a comment |
This is a bit tricky. The type will be part of .NET Core 3.0, it does not ship as part of .NET Core 2.0 or 2.1, but is available via an additional NuGet package (System.Security.Permissions).
The tools and documentation may have a different view on what is "part of" a particular version of .NET Core and what is "usable" in some way on a particular version.
An additional source you can check is apisof.net: https://apisof.net/catalog/System.Security.Permissions.FileIOPermissionAccess
which correctly lists the type as .NET Core 3.0 and ".NET Core + Platform Extensions" 2.0 and 2.1
answered Nov 20 '18 at 11:04
Martin UllrichMartin Ullrich
45.7k7124126
Ok I understand now. Indeed, I found in the analyzer settings the options ".NET Core/Standard + Platform Extensions". When checked, the resultant column is consistent with the results found with the API Browser. Thanks also for the additional resource.
– Mr Davies
Nov 20 '18 at 11:24
add a comment |
This is a bit tricky. The type will be part of .NET Core 3.0, it does not ship as part of .NET Core 2.0 or 2.1, but is available via an additional NuGet package (System.Security.Permissions).
The tools and documentation may have a different view on what is "part of" a particular version of .NET Core and what is "usable" in some way on a particular version.
An additional source you can check is apisof.net: https://apisof.net/catalog/System.Security.Permissions.FileIOPermissionAccess
which correctly lists the type as .NET Core 3.0 and ".NET Core + Platform Extensions" 2.0 and 2.1
answered Nov 20 '18 at 11:04
Martin UllrichMartin Ullrich
45.7k7124126
This is a bit tricky. The type will be part of .NET Core 3.0, it does not ship as part of .NET Core 2.0 or 2.1, but is available via an additional NuGet package (System.Security.Permissions).
The tools and documentation may have a different view on what is "part of" a particular version of .NET Core and what is "usable" in some way on a particular version.
An additional source you can check is apisof.net: https://apisof.net/catalog/System.Security.Permissions.FileIOPermissionAccess
which correctly lists the type as .NET Core 3.0 and ".NET Core + Platform Extensions" 2.0 and 2.1
answered Nov 20 '18 at 11:04
Martin UllrichMartin Ullrich
45.7k7124126
answered Nov 20 '18 at 11:04
Martin UllrichMartin Ullrich
45.7k7124126
answered Nov 20 '18 at 11:04
Martin UllrichMartin Ullrich
45.7k7124126
answered Nov 20 '18 at 11:04
Martin UllrichMartin Ullrich
45.7k7124126
45.7k7124126
Ok I understand now. Indeed, I found in the analyzer settings the options ".NET Core/Standard + Platform Extensions". When checked, the resultant column is consistent with the results found with the API Browser. Thanks also for the additional resource.
– Mr Davies
Nov 20 '18 at 11:24
add a comment |
Ok I understand now. Indeed, I found in the analyzer settings the options ".NET Core/Standard + Platform Extensions". When checked, the resultant column is consistent with the results found with the API Browser. Thanks also for the additional resource.
– Mr Davies
Nov 20 '18 at 11:24
Ok I understand now. Indeed, I found in the analyzer settings the options ".NET Core/Standard + Platform Extensions". When checked, the resultant column is consistent with the results found with the API Browser. Thanks also for the additional resource.
– Mr Davies
Nov 20 '18 at 11:24
Ok I understand now. Indeed, I found in the analyzer settings the options ".NET Core/Standard + Platform Extensions". When checked, the resultant column is consistent with the results found with the API Browser. Thanks also for the additional resource.
– Mr Davies
Nov 20 '18 at 11:24
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53390956%2fnet-portability-analyzer-doesnt-match-net-api-browser-results%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
