What is .NET Multi-Targeting Pack?
Installing Visual Studio installs a bunch of .Net packages called
- .NET x Targeting Pack
- .NET x Multi-Targeting Pack
- .NET x Multi-Targeting Pack (ENU)
Where "x" stands for the .Net version number it supports. What are these packages for?
.net-framework visual-studio c#
add a comment |
Installing Visual Studio installs a bunch of .Net packages called
- .NET x Targeting Pack
- .NET x Multi-Targeting Pack
- .NET x Multi-Targeting Pack (ENU)
Where "x" stands for the .Net version number it supports. What are these packages for?
.net-framework visual-studio c#
add a comment |
Installing Visual Studio installs a bunch of .Net packages called
- .NET x Targeting Pack
- .NET x Multi-Targeting Pack
- .NET x Multi-Targeting Pack (ENU)
Where "x" stands for the .Net version number it supports. What are these packages for?
.net-framework visual-studio c#
Installing Visual Studio installs a bunch of .Net packages called
- .NET x Targeting Pack
- .NET x Multi-Targeting Pack
- .NET x Multi-Targeting Pack (ENU)
Where "x" stands for the .Net version number it supports. What are these packages for?
.net-framework visual-studio c#
.net-framework visual-studio c#
edited Feb 5 at 8:43
NoNameProvided
asked Feb 11 '16 at 9:46
NoNameProvidedNoNameProvided
1,72121223
1,72121223
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
It can be best explained by the following description.
A multi-targeting pack, or MT pack, is a set of reference assemblies
that corresponds to a particular .NET Framework platform and version.
A reference assembly is a .NET Framework assembly that typically has
no method bodies and no internal or private APIs. Reference assemblies
contain just the information a compiler needs.
For example, there are multi-targeting packs for the .NET Framework
3.5, the .NET Framework 4, Update 4.0.x for the .NET Framework 4, the .NET Framework 4.5, Windows Phone 7.5, Windows Metro style apps,
Portable Class Library, and so on.
Visual Studio installs a set of multi-targeting packs, and so do SDKs
such as the Visual Studio SDK, the Silverlight SDK, and the Windows
Phone SDK. Typically, multi-targeting packs are installed under
“%ProgramFiles(x86)%Reference AssembliesMicrosoftFramework”
or“%ProgramFiles%Reference AssembliesMicrosoftFramework”
on a 32-bit
computer).
The following image from Microsoft provides clarity to the above description.
Do I need these packages if I only want to use Visual Studio to
make WP10 Mobile applications?
If you only are going to target Windows Phone 10 then having the packages installed isn't required to publish your application to the Windows Store. You can't target unsupported versions of the .NET Framework, and publish your application to the Windows Store, which means that all your assemblies will be compiled against the same version of the .NET Framework anyways.
Source: Multi-Targeting Guidelines for Tools for Managed Code [Mircea]
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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%2fsuperuser.com%2fquestions%2f1038423%2fwhat-is-net-multi-targeting-pack%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
It can be best explained by the following description.
A multi-targeting pack, or MT pack, is a set of reference assemblies
that corresponds to a particular .NET Framework platform and version.
A reference assembly is a .NET Framework assembly that typically has
no method bodies and no internal or private APIs. Reference assemblies
contain just the information a compiler needs.
For example, there are multi-targeting packs for the .NET Framework
3.5, the .NET Framework 4, Update 4.0.x for the .NET Framework 4, the .NET Framework 4.5, Windows Phone 7.5, Windows Metro style apps,
Portable Class Library, and so on.
Visual Studio installs a set of multi-targeting packs, and so do SDKs
such as the Visual Studio SDK, the Silverlight SDK, and the Windows
Phone SDK. Typically, multi-targeting packs are installed under
“%ProgramFiles(x86)%Reference AssembliesMicrosoftFramework”
or“%ProgramFiles%Reference AssembliesMicrosoftFramework”
on a 32-bit
computer).
The following image from Microsoft provides clarity to the above description.
Do I need these packages if I only want to use Visual Studio to
make WP10 Mobile applications?
If you only are going to target Windows Phone 10 then having the packages installed isn't required to publish your application to the Windows Store. You can't target unsupported versions of the .NET Framework, and publish your application to the Windows Store, which means that all your assemblies will be compiled against the same version of the .NET Framework anyways.
Source: Multi-Targeting Guidelines for Tools for Managed Code [Mircea]
add a comment |
It can be best explained by the following description.
A multi-targeting pack, or MT pack, is a set of reference assemblies
that corresponds to a particular .NET Framework platform and version.
A reference assembly is a .NET Framework assembly that typically has
no method bodies and no internal or private APIs. Reference assemblies
contain just the information a compiler needs.
For example, there are multi-targeting packs for the .NET Framework
3.5, the .NET Framework 4, Update 4.0.x for the .NET Framework 4, the .NET Framework 4.5, Windows Phone 7.5, Windows Metro style apps,
Portable Class Library, and so on.
Visual Studio installs a set of multi-targeting packs, and so do SDKs
such as the Visual Studio SDK, the Silverlight SDK, and the Windows
Phone SDK. Typically, multi-targeting packs are installed under
“%ProgramFiles(x86)%Reference AssembliesMicrosoftFramework”
or“%ProgramFiles%Reference AssembliesMicrosoftFramework”
on a 32-bit
computer).
The following image from Microsoft provides clarity to the above description.
Do I need these packages if I only want to use Visual Studio to
make WP10 Mobile applications?
If you only are going to target Windows Phone 10 then having the packages installed isn't required to publish your application to the Windows Store. You can't target unsupported versions of the .NET Framework, and publish your application to the Windows Store, which means that all your assemblies will be compiled against the same version of the .NET Framework anyways.
Source: Multi-Targeting Guidelines for Tools for Managed Code [Mircea]
add a comment |
It can be best explained by the following description.
A multi-targeting pack, or MT pack, is a set of reference assemblies
that corresponds to a particular .NET Framework platform and version.
A reference assembly is a .NET Framework assembly that typically has
no method bodies and no internal or private APIs. Reference assemblies
contain just the information a compiler needs.
For example, there are multi-targeting packs for the .NET Framework
3.5, the .NET Framework 4, Update 4.0.x for the .NET Framework 4, the .NET Framework 4.5, Windows Phone 7.5, Windows Metro style apps,
Portable Class Library, and so on.
Visual Studio installs a set of multi-targeting packs, and so do SDKs
such as the Visual Studio SDK, the Silverlight SDK, and the Windows
Phone SDK. Typically, multi-targeting packs are installed under
“%ProgramFiles(x86)%Reference AssembliesMicrosoftFramework”
or“%ProgramFiles%Reference AssembliesMicrosoftFramework”
on a 32-bit
computer).
The following image from Microsoft provides clarity to the above description.
Do I need these packages if I only want to use Visual Studio to
make WP10 Mobile applications?
If you only are going to target Windows Phone 10 then having the packages installed isn't required to publish your application to the Windows Store. You can't target unsupported versions of the .NET Framework, and publish your application to the Windows Store, which means that all your assemblies will be compiled against the same version of the .NET Framework anyways.
Source: Multi-Targeting Guidelines for Tools for Managed Code [Mircea]
It can be best explained by the following description.
A multi-targeting pack, or MT pack, is a set of reference assemblies
that corresponds to a particular .NET Framework platform and version.
A reference assembly is a .NET Framework assembly that typically has
no method bodies and no internal or private APIs. Reference assemblies
contain just the information a compiler needs.
For example, there are multi-targeting packs for the .NET Framework
3.5, the .NET Framework 4, Update 4.0.x for the .NET Framework 4, the .NET Framework 4.5, Windows Phone 7.5, Windows Metro style apps,
Portable Class Library, and so on.
Visual Studio installs a set of multi-targeting packs, and so do SDKs
such as the Visual Studio SDK, the Silverlight SDK, and the Windows
Phone SDK. Typically, multi-targeting packs are installed under
“%ProgramFiles(x86)%Reference AssembliesMicrosoftFramework”
or“%ProgramFiles%Reference AssembliesMicrosoftFramework”
on a 32-bit
computer).
The following image from Microsoft provides clarity to the above description.
Do I need these packages if I only want to use Visual Studio to
make WP10 Mobile applications?
If you only are going to target Windows Phone 10 then having the packages installed isn't required to publish your application to the Windows Store. You can't target unsupported versions of the .NET Framework, and publish your application to the Windows Store, which means that all your assemblies will be compiled against the same version of the .NET Framework anyways.
Source: Multi-Targeting Guidelines for Tools for Managed Code [Mircea]
edited Mar 19 '18 at 8:12
Samir
11.3k57143205
11.3k57143205
answered Feb 11 '16 at 13:31
RamhoundRamhound
20.6k156286
20.6k156286
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- 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%2fsuperuser.com%2fquestions%2f1038423%2fwhat-is-net-multi-targeting-pack%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