Way to run .NET application on Win7 without installing anything?
We have a few special computers that are for security reasons offline and use W7 with some tweaks. I cannot install anything on these machines, all I can do is run a portable program.
I would need to run my .NET application, is there any way I could run it without having to install .NET framework; something like pre-compiling it with linked all the libraries and then run it as a stand-alone app, like .NET native does for W10?
windows-7 .net-framework portable
edited Dec 30 '18 at 0:29
fixer1234
18.1k144681
asked Dec 29 '18 at 10:52
John VJohn V
1102
add a comment |
We have a few special computers that are for security reasons offline and use W7 with some tweaks. I cannot install anything on these machines, all I can do is run a portable program.
I would need to run my .NET application, is there any way I could run it without having to install .NET framework; something like pre-compiling it with linked all the libraries and then run it as a stand-alone app, like .NET native does for W10?
windows-7 .net-framework portable
edited Dec 30 '18 at 0:29
fixer1234
18.1k144681
asked Dec 29 '18 at 10:52
John VJohn V
1102
add a comment |
We have a few special computers that are for security reasons offline and use W7 with some tweaks. I cannot install anything on these machines, all I can do is run a portable program.
I would need to run my .NET application, is there any way I could run it without having to install .NET framework; something like pre-compiling it with linked all the libraries and then run it as a stand-alone app, like .NET native does for W10?
windows-7 .net-framework portable
edited Dec 30 '18 at 0:29
fixer1234
18.1k144681
asked Dec 29 '18 at 10:52
John VJohn V
1102
We have a few special computers that are for security reasons offline and use W7 with some tweaks. I cannot install anything on these machines, all I can do is run a portable program.
I would need to run my .NET application, is there any way I could run it without having to install .NET framework; something like pre-compiling it with linked all the libraries and then run it as a stand-alone app, like .NET native does for W10?
windows-7 .net-framework portable
windows-7 .net-framework portable
edited Dec 30 '18 at 0:29
fixer1234
18.1k144681
asked Dec 29 '18 at 10:52
John VJohn V
1102
edited Dec 30 '18 at 0:29
fixer1234
18.1k144681
asked Dec 29 '18 at 10:52
John VJohn V
1102
edited Dec 30 '18 at 0:29
fixer1234
18.1k144681
edited Dec 30 '18 at 0:29
fixer1234
18.1k144681
edited Dec 30 '18 at 0:29
fixer1234
18.1k144681
18.1k144681
asked Dec 29 '18 at 10:52
John VJohn V
1102
asked Dec 29 '18 at 10:52
John VJohn V
1102
asked Dec 29 '18 at 10:52
John VJohn V
1102
1102
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
According to the article
What version of the .NET Framework is included in what version of the OS,
Windows 7 includes the .NET Framework 3.5.1 as an OS component.
This means you will have available the .NET Framework 2.0 SP2, 3.0 SP2
and 3.5 SP1 plus a few post 3.5 SP1 bug fixes.
You will not see it in Programs and Features because it is built-in.
So all you have to do is to downgrade your app to .NET 3 and it will run.
If you are using Visual Studio 2017, it might be possible to package the
.Net Framework with the application. See the Microsoft blog:
Package a .NET desktop application using the Desktop Bridge and Visual Studio Preview.
answered Dec 29 '18 at 11:18
harrymcharrymc
255k14265566
The thing you say about packaging a .NET application with Desktop Bridge is only relevant for Win10, and refers to a way to distribute non-Windows-Store apps (either Win32 or .NET) through the Windows Store. It has nothing to do with packaging an entire .NET framework with your app; in fact, Desktop Bridge apps, if they use .NET at all, need to target a specific version of it (4.6.2, if memory serves). With that said, the stuff about just making your app target .NET 2.0-3.5.1 and distributing it as-is will work for Win7 (just don't package it in a Win10 .APPX bundle!)
– CBHacking
Dec 30 '18 at 8:33
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%2f1388706%2fway-to-run-net-application-on-win7-without-installing-anything%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
According to the article
What version of the .NET Framework is included in what version of the OS,
Windows 7 includes the .NET Framework 3.5.1 as an OS component.
This means you will have available the .NET Framework 2.0 SP2, 3.0 SP2
and 3.5 SP1 plus a few post 3.5 SP1 bug fixes.
You will not see it in Programs and Features because it is built-in.
So all you have to do is to downgrade your app to .NET 3 and it will run.
If you are using Visual Studio 2017, it might be possible to package the
.Net Framework with the application. See the Microsoft blog:
Package a .NET desktop application using the Desktop Bridge and Visual Studio Preview.
answered Dec 29 '18 at 11:18
harrymcharrymc
255k14265566
The thing you say about packaging a .NET application with Desktop Bridge is only relevant for Win10, and refers to a way to distribute non-Windows-Store apps (either Win32 or .NET) through the Windows Store. It has nothing to do with packaging an entire .NET framework with your app; in fact, Desktop Bridge apps, if they use .NET at all, need to target a specific version of it (4.6.2, if memory serves). With that said, the stuff about just making your app target .NET 2.0-3.5.1 and distributing it as-is will work for Win7 (just don't package it in a Win10 .APPX bundle!)
– CBHacking
Dec 30 '18 at 8:33
add a comment |
According to the article
What version of the .NET Framework is included in what version of the OS,
Windows 7 includes the .NET Framework 3.5.1 as an OS component.
This means you will have available the .NET Framework 2.0 SP2, 3.0 SP2
and 3.5 SP1 plus a few post 3.5 SP1 bug fixes.
You will not see it in Programs and Features because it is built-in.
So all you have to do is to downgrade your app to .NET 3 and it will run.
If you are using Visual Studio 2017, it might be possible to package the
.Net Framework with the application. See the Microsoft blog:
Package a .NET desktop application using the Desktop Bridge and Visual Studio Preview.
answered Dec 29 '18 at 11:18
harrymcharrymc
255k14265566
The thing you say about packaging a .NET application with Desktop Bridge is only relevant for Win10, and refers to a way to distribute non-Windows-Store apps (either Win32 or .NET) through the Windows Store. It has nothing to do with packaging an entire .NET framework with your app; in fact, Desktop Bridge apps, if they use .NET at all, need to target a specific version of it (4.6.2, if memory serves). With that said, the stuff about just making your app target .NET 2.0-3.5.1 and distributing it as-is will work for Win7 (just don't package it in a Win10 .APPX bundle!)
– CBHacking
Dec 30 '18 at 8:33
add a comment |
According to the article
What version of the .NET Framework is included in what version of the OS,
Windows 7 includes the .NET Framework 3.5.1 as an OS component.
This means you will have available the .NET Framework 2.0 SP2, 3.0 SP2
and 3.5 SP1 plus a few post 3.5 SP1 bug fixes.
You will not see it in Programs and Features because it is built-in.
So all you have to do is to downgrade your app to .NET 3 and it will run.
If you are using Visual Studio 2017, it might be possible to package the
.Net Framework with the application. See the Microsoft blog:
Package a .NET desktop application using the Desktop Bridge and Visual Studio Preview.
answered Dec 29 '18 at 11:18
harrymcharrymc
255k14265566
According to the article
What version of the .NET Framework is included in what version of the OS,
Windows 7 includes the .NET Framework 3.5.1 as an OS component.
This means you will have available the .NET Framework 2.0 SP2, 3.0 SP2
and 3.5 SP1 plus a few post 3.5 SP1 bug fixes.
You will not see it in Programs and Features because it is built-in.
So all you have to do is to downgrade your app to .NET 3 and it will run.
If you are using Visual Studio 2017, it might be possible to package the
.Net Framework with the application. See the Microsoft blog:
Package a .NET desktop application using the Desktop Bridge and Visual Studio Preview.
answered Dec 29 '18 at 11:18
harrymcharrymc
255k14265566
edited Dec 30 '18 at 7:03
answered Dec 29 '18 at 11:18
harrymcharrymc
255k14265566
answered Dec 29 '18 at 11:18
harrymcharrymc
255k14265566
answered Dec 29 '18 at 11:18
harrymcharrymc
255k14265566
255k14265566
The thing you say about packaging a .NET application with Desktop Bridge is only relevant for Win10, and refers to a way to distribute non-Windows-Store apps (either Win32 or .NET) through the Windows Store. It has nothing to do with packaging an entire .NET framework with your app; in fact, Desktop Bridge apps, if they use .NET at all, need to target a specific version of it (4.6.2, if memory serves). With that said, the stuff about just making your app target .NET 2.0-3.5.1 and distributing it as-is will work for Win7 (just don't package it in a Win10 .APPX bundle!)
– CBHacking
Dec 30 '18 at 8:33
add a comment |
The thing you say about packaging a .NET application with Desktop Bridge is only relevant for Win10, and refers to a way to distribute non-Windows-Store apps (either Win32 or .NET) through the Windows Store. It has nothing to do with packaging an entire .NET framework with your app; in fact, Desktop Bridge apps, if they use .NET at all, need to target a specific version of it (4.6.2, if memory serves). With that said, the stuff about just making your app target .NET 2.0-3.5.1 and distributing it as-is will work for Win7 (just don't package it in a Win10 .APPX bundle!)
– CBHacking
Dec 30 '18 at 8:33
The thing you say about packaging a .NET application with Desktop Bridge is only relevant for Win10, and refers to a way to distribute non-Windows-Store apps (either Win32 or .NET) through the Windows Store. It has nothing to do with packaging an entire .NET framework with your app; in fact, Desktop Bridge apps, if they use .NET at all, need to target a specific version of it (4.6.2, if memory serves). With that said, the stuff about just making your app target .NET 2.0-3.5.1 and distributing it as-is will work for Win7 (just don't package it in a Win10 .APPX bundle!)
– CBHacking
Dec 30 '18 at 8:33
The thing you say about packaging a .NET application with Desktop Bridge is only relevant for Win10, and refers to a way to distribute non-Windows-Store apps (either Win32 or .NET) through the Windows Store. It has nothing to do with packaging an entire .NET framework with your app; in fact, Desktop Bridge apps, if they use .NET at all, need to target a specific version of it (4.6.2, if memory serves). With that said, the stuff about just making your app target .NET 2.0-3.5.1 and distributing it as-is will work for Win7 (just don't package it in a Win10 .APPX bundle!)
– CBHacking
Dec 30 '18 at 8:33
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%2f1388706%2fway-to-run-net-application-on-win7-without-installing-anything%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
