Mixing
Add a setting to app.config or will adding the setting to *.exe.config be suffice?
A recent article:
https://blogs.msdn.microsoft.com/dotnet/2017/04/05/announcing-the-net-framework-4-7/
announces a possible fix for intermittent problems with touch screen support. As I read the document, one only needs to change the app.config file. See the line:
"You can opt-into the new touch implementation with the following app.config entry.
<runtime>
<AppContextSwitchOverrides value="Switch.System.Windows.Input.Stylus.EnablePointerSupport=true"/>
</runtime>
under section:
WPF Touch/Stylus support for Windows 10
My question is: Can I just make the change in Myapp.exe.config or must I actually make it in app.config? Perhaps the question could be: Is the app.config info used at compile time or just translated into myapp.exe.config?
Further, I'd like to know if it's ok to leave:
<startup>
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.5"/>
</startup>
The documentation just mentions adding EnablePointerSupport and makes no mention of changing the Version in the config file. I did in fact download the .NET Framework 4.7 and install, but have not changed the Version in the config file. Do I need to?
Thanks.
c# windows touch app-config
edited Nov 27 '18 at 5:12
Jeremy Thompson
39.3k13102199
asked Nov 19 '18 at 19:11
DaveDave
2,64293968
add a comment |
A recent article:
https://blogs.msdn.microsoft.com/dotnet/2017/04/05/announcing-the-net-framework-4-7/
announces a possible fix for intermittent problems with touch screen support. As I read the document, one only needs to change the app.config file. See the line:
"You can opt-into the new touch implementation with the following app.config entry.
<runtime>
<AppContextSwitchOverrides value="Switch.System.Windows.Input.Stylus.EnablePointerSupport=true"/>
</runtime>
under section:
WPF Touch/Stylus support for Windows 10
My question is: Can I just make the change in Myapp.exe.config or must I actually make it in app.config? Perhaps the question could be: Is the app.config info used at compile time or just translated into myapp.exe.config?
Further, I'd like to know if it's ok to leave:
<startup>
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.5"/>
</startup>
The documentation just mentions adding EnablePointerSupport and makes no mention of changing the Version in the config file. I did in fact download the .NET Framework 4.7 and install, but have not changed the Version in the config file. Do I need to?
Thanks.
c# windows touch app-config
edited Nov 27 '18 at 5:12
Jeremy Thompson
39.3k13102199
asked Nov 19 '18 at 19:11
DaveDave
2,64293968
1
Hi Dave I spent a bit of time helping you out. If you have any questions let me know?
– Jeremy Thompson
Nov 30 '18 at 5:29
Thanks Jeremy! Very much appreciated.
– Dave
Dec 1 '18 at 6:14
Update for future readers.... In my case these fixes did not solve our intermittent scrollbar problems. We're still searching for the root cause (which could be hardware, drivers, etc. Not necessarily software). But I think we are now at least using Framework 4.7 and the potential fix correctly and can cross that off our list.
– Dave
Dec 1 '18 at 6:16
add a comment |
A recent article:
https://blogs.msdn.microsoft.com/dotnet/2017/04/05/announcing-the-net-framework-4-7/
announces a possible fix for intermittent problems with touch screen support. As I read the document, one only needs to change the app.config file. See the line:
"You can opt-into the new touch implementation with the following app.config entry.
<runtime>
<AppContextSwitchOverrides value="Switch.System.Windows.Input.Stylus.EnablePointerSupport=true"/>
</runtime>
under section:
WPF Touch/Stylus support for Windows 10
My question is: Can I just make the change in Myapp.exe.config or must I actually make it in app.config? Perhaps the question could be: Is the app.config info used at compile time or just translated into myapp.exe.config?
Further, I'd like to know if it's ok to leave:
<startup>
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.5"/>
</startup>
The documentation just mentions adding EnablePointerSupport and makes no mention of changing the Version in the config file. I did in fact download the .NET Framework 4.7 and install, but have not changed the Version in the config file. Do I need to?
Thanks.
c# windows touch app-config
edited Nov 27 '18 at 5:12
Jeremy Thompson
39.3k13102199
asked Nov 19 '18 at 19:11
DaveDave
2,64293968
A recent article:
https://blogs.msdn.microsoft.com/dotnet/2017/04/05/announcing-the-net-framework-4-7/
announces a possible fix for intermittent problems with touch screen support. As I read the document, one only needs to change the app.config file. See the line:
"You can opt-into the new touch implementation with the following app.config entry.
<runtime>
<AppContextSwitchOverrides value="Switch.System.Windows.Input.Stylus.EnablePointerSupport=true"/>
</runtime>
under section:
WPF Touch/Stylus support for Windows 10
My question is: Can I just make the change in Myapp.exe.config or must I actually make it in app.config? Perhaps the question could be: Is the app.config info used at compile time or just translated into myapp.exe.config?
Further, I'd like to know if it's ok to leave:
<startup>
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.5"/>
</startup>
The documentation just mentions adding EnablePointerSupport and makes no mention of changing the Version in the config file. I did in fact download the .NET Framework 4.7 and install, but have not changed the Version in the config file. Do I need to?
Thanks.
c# windows touch app-config
c# windows touch app-config
edited Nov 27 '18 at 5:12
Jeremy Thompson
39.3k13102199
asked Nov 19 '18 at 19:11
DaveDave
2,64293968
edited Nov 27 '18 at 5:12
Jeremy Thompson
39.3k13102199
asked Nov 19 '18 at 19:11
DaveDave
2,64293968
edited Nov 27 '18 at 5:12
Jeremy Thompson
39.3k13102199
edited Nov 27 '18 at 5:12
Jeremy Thompson
39.3k13102199
edited Nov 27 '18 at 5:12
Jeremy Thompson
39.3k13102199
39.3k13102199
asked Nov 19 '18 at 19:11
DaveDave
2,64293968
asked Nov 19 '18 at 19:11
DaveDave
2,64293968
asked Nov 19 '18 at 19:11
DaveDave
2,64293968
2,64293968
1
Hi Dave I spent a bit of time helping you out. If you have any questions let me know?
– Jeremy Thompson
Nov 30 '18 at 5:29
Thanks Jeremy! Very much appreciated.
– Dave
Dec 1 '18 at 6:14
Update for future readers.... In my case these fixes did not solve our intermittent scrollbar problems. We're still searching for the root cause (which could be hardware, drivers, etc. Not necessarily software). But I think we are now at least using Framework 4.7 and the potential fix correctly and can cross that off our list.
– Dave
Dec 1 '18 at 6:16
add a comment |
1
Hi Dave I spent a bit of time helping you out. If you have any questions let me know?
– Jeremy Thompson
Nov 30 '18 at 5:29
Thanks Jeremy! Very much appreciated.
– Dave
Dec 1 '18 at 6:14
Update for future readers.... In my case these fixes did not solve our intermittent scrollbar problems. We're still searching for the root cause (which could be hardware, drivers, etc. Not necessarily software). But I think we are now at least using Framework 4.7 and the potential fix correctly and can cross that off our list.
– Dave
Dec 1 '18 at 6:16
1
1
Hi Dave I spent a bit of time helping you out. If you have any questions let me know?
– Jeremy Thompson
Nov 30 '18 at 5:29
Hi Dave I spent a bit of time helping you out. If you have any questions let me know?
– Jeremy Thompson
Nov 30 '18 at 5:29
Thanks Jeremy! Very much appreciated.
– Dave
Dec 1 '18 at 6:14
Thanks Jeremy! Very much appreciated.
– Dave
Dec 1 '18 at 6:14
Update for future readers.... In my case these fixes did not solve our intermittent scrollbar problems. We're still searching for the root cause (which could be hardware, drivers, etc. Not necessarily software). But I think we are now at least using Framework 4.7 and the potential fix correctly and can cross that off our list.
– Dave
Dec 1 '18 at 6:16
Update for future readers.... In my case these fixes did not solve our intermittent scrollbar problems. We're still searching for the root cause (which could be hardware, drivers, etc. Not necessarily software). But I think we are now at least using Framework 4.7 and the potential fix correctly and can cross that off our list.
– Dave
Dec 1 '18 at 6:16
add a comment |
1 Answer
1
active
oldest
votes
Can I just make the change in Myapp.exe.config or must I actually make it in app.config?
If your EXE is deployed you can change the App.Exe.Config, restart the application and the new config settings will be used. If you do this for an ASP.Net application (ie. change the web.config) it will cause the App Pool in IIS to be recycled and new web.config settings to be used.
Obviously add any changes to the actual App.Config so next time you compile its added automatically to the output App.Exe.Config.
You will have some more questions about this and its all documented here, do go through this its a good read:
https://docs.microsoft.com/en-us/dotnet/framework/migration-guide/how-to-configure-an-app-to-support-net-framework-4-or-4-5
The documentation just mentions adding EnablePointerSupport and makes no mention of changing the Version in the config file. I did in fact download the .NET Framework 4.7 and install, but have not changed the Version in the config file. Do I need to?
Unless you're using .Net 4.7 specific features you can leave the version as .Net 4.5.
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.5"/>
In this case, the article specifically states its a bug fix in .Net 4.7. So you will need to use 4.7.
To change this you edit the Project's Build tab properties (or manually in the config file).
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.7"/>
Here is a reference to the .Net Frameworks vs SKU's:
https://docs.microsoft.com/en-us/dotnet/framework/configure-apps/file-schema/startup/supportedruntime-element
If app.config is used at compile time for anything other than producing the Myapp.exe.config file.
You're right it's used at Compile time to generate the App.Exe.Config.
Many people store configuration settings in config files, so an App.Exe.Config can be edited at run-time as well. At the end of the day its simply an XML file.
Also note you can have Transforms on your App.Configs for different environments at design-time:
answered Nov 27 '18 at 3:13
Jeremy ThompsonJeremy Thompson
39.3k13102199
Thanks Jeremy and sorry for the delay. Marked as answer!
– Dave
Dec 1 '18 at 6:13
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%2f53381140%2fadd-a-setting-to-app-config-or-will-adding-the-setting-to-exe-config-be-suffic%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
Can I just make the change in Myapp.exe.config or must I actually make it in app.config?
If your EXE is deployed you can change the App.Exe.Config, restart the application and the new config settings will be used. If you do this for an ASP.Net application (ie. change the web.config) it will cause the App Pool in IIS to be recycled and new web.config settings to be used.
Obviously add any changes to the actual App.Config so next time you compile its added automatically to the output App.Exe.Config.
You will have some more questions about this and its all documented here, do go through this its a good read:
https://docs.microsoft.com/en-us/dotnet/framework/migration-guide/how-to-configure-an-app-to-support-net-framework-4-or-4-5
The documentation just mentions adding EnablePointerSupport and makes no mention of changing the Version in the config file. I did in fact download the .NET Framework 4.7 and install, but have not changed the Version in the config file. Do I need to?
Unless you're using .Net 4.7 specific features you can leave the version as .Net 4.5.
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.5"/>
In this case, the article specifically states its a bug fix in .Net 4.7. So you will need to use 4.7.
To change this you edit the Project's Build tab properties (or manually in the config file).
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.7"/>
Here is a reference to the .Net Frameworks vs SKU's:
https://docs.microsoft.com/en-us/dotnet/framework/configure-apps/file-schema/startup/supportedruntime-element
If app.config is used at compile time for anything other than producing the Myapp.exe.config file.
You're right it's used at Compile time to generate the App.Exe.Config.
Many people store configuration settings in config files, so an App.Exe.Config can be edited at run-time as well. At the end of the day its simply an XML file.
Also note you can have Transforms on your App.Configs for different environments at design-time:
answered Nov 27 '18 at 3:13
Jeremy ThompsonJeremy Thompson
39.3k13102199
Thanks Jeremy and sorry for the delay. Marked as answer!
– Dave
Dec 1 '18 at 6:13
add a comment |
Can I just make the change in Myapp.exe.config or must I actually make it in app.config?
If your EXE is deployed you can change the App.Exe.Config, restart the application and the new config settings will be used. If you do this for an ASP.Net application (ie. change the web.config) it will cause the App Pool in IIS to be recycled and new web.config settings to be used.
Obviously add any changes to the actual App.Config so next time you compile its added automatically to the output App.Exe.Config.
You will have some more questions about this and its all documented here, do go through this its a good read:
https://docs.microsoft.com/en-us/dotnet/framework/migration-guide/how-to-configure-an-app-to-support-net-framework-4-or-4-5
The documentation just mentions adding EnablePointerSupport and makes no mention of changing the Version in the config file. I did in fact download the .NET Framework 4.7 and install, but have not changed the Version in the config file. Do I need to?
Unless you're using .Net 4.7 specific features you can leave the version as .Net 4.5.
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.5"/>
In this case, the article specifically states its a bug fix in .Net 4.7. So you will need to use 4.7.
To change this you edit the Project's Build tab properties (or manually in the config file).
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.7"/>
Here is a reference to the .Net Frameworks vs SKU's:
https://docs.microsoft.com/en-us/dotnet/framework/configure-apps/file-schema/startup/supportedruntime-element
If app.config is used at compile time for anything other than producing the Myapp.exe.config file.
You're right it's used at Compile time to generate the App.Exe.Config.
Many people store configuration settings in config files, so an App.Exe.Config can be edited at run-time as well. At the end of the day its simply an XML file.
Also note you can have Transforms on your App.Configs for different environments at design-time:
answered Nov 27 '18 at 3:13
Jeremy ThompsonJeremy Thompson
39.3k13102199
Thanks Jeremy and sorry for the delay. Marked as answer!
– Dave
Dec 1 '18 at 6:13
add a comment |
Can I just make the change in Myapp.exe.config or must I actually make it in app.config?
If your EXE is deployed you can change the App.Exe.Config, restart the application and the new config settings will be used. If you do this for an ASP.Net application (ie. change the web.config) it will cause the App Pool in IIS to be recycled and new web.config settings to be used.
Obviously add any changes to the actual App.Config so next time you compile its added automatically to the output App.Exe.Config.
You will have some more questions about this and its all documented here, do go through this its a good read:
https://docs.microsoft.com/en-us/dotnet/framework/migration-guide/how-to-configure-an-app-to-support-net-framework-4-or-4-5
The documentation just mentions adding EnablePointerSupport and makes no mention of changing the Version in the config file. I did in fact download the .NET Framework 4.7 and install, but have not changed the Version in the config file. Do I need to?
Unless you're using .Net 4.7 specific features you can leave the version as .Net 4.5.
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.5"/>
In this case, the article specifically states its a bug fix in .Net 4.7. So you will need to use 4.7.
To change this you edit the Project's Build tab properties (or manually in the config file).
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.7"/>
Here is a reference to the .Net Frameworks vs SKU's:
https://docs.microsoft.com/en-us/dotnet/framework/configure-apps/file-schema/startup/supportedruntime-element
If app.config is used at compile time for anything other than producing the Myapp.exe.config file.
You're right it's used at Compile time to generate the App.Exe.Config.
Many people store configuration settings in config files, so an App.Exe.Config can be edited at run-time as well. At the end of the day its simply an XML file.
Also note you can have Transforms on your App.Configs for different environments at design-time:
answered Nov 27 '18 at 3:13
Jeremy ThompsonJeremy Thompson
39.3k13102199
Can I just make the change in Myapp.exe.config or must I actually make it in app.config?
If your EXE is deployed you can change the App.Exe.Config, restart the application and the new config settings will be used. If you do this for an ASP.Net application (ie. change the web.config) it will cause the App Pool in IIS to be recycled and new web.config settings to be used.
Obviously add any changes to the actual App.Config so next time you compile its added automatically to the output App.Exe.Config.
You will have some more questions about this and its all documented here, do go through this its a good read:
https://docs.microsoft.com/en-us/dotnet/framework/migration-guide/how-to-configure-an-app-to-support-net-framework-4-or-4-5
The documentation just mentions adding EnablePointerSupport and makes no mention of changing the Version in the config file. I did in fact download the .NET Framework 4.7 and install, but have not changed the Version in the config file. Do I need to?
Unless you're using .Net 4.7 specific features you can leave the version as .Net 4.5.
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.5"/>
In this case, the article specifically states its a bug fix in .Net 4.7. So you will need to use 4.7.
To change this you edit the Project's Build tab properties (or manually in the config file).
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.7"/>
Here is a reference to the .Net Frameworks vs SKU's:
https://docs.microsoft.com/en-us/dotnet/framework/configure-apps/file-schema/startup/supportedruntime-element
If app.config is used at compile time for anything other than producing the Myapp.exe.config file.
You're right it's used at Compile time to generate the App.Exe.Config.
Many people store configuration settings in config files, so an App.Exe.Config can be edited at run-time as well. At the end of the day its simply an XML file.
Also note you can have Transforms on your App.Configs for different environments at design-time:
answered Nov 27 '18 at 3:13
Jeremy ThompsonJeremy Thompson
39.3k13102199
edited Nov 27 '18 at 4:33
answered Nov 27 '18 at 3:13
Jeremy ThompsonJeremy Thompson
39.3k13102199
answered Nov 27 '18 at 3:13
Jeremy ThompsonJeremy Thompson
39.3k13102199
answered Nov 27 '18 at 3:13
Jeremy ThompsonJeremy Thompson
39.3k13102199
39.3k13102199
Thanks Jeremy and sorry for the delay. Marked as answer!
– Dave
Dec 1 '18 at 6:13
add a comment |
Thanks Jeremy and sorry for the delay. Marked as answer!
– Dave
Dec 1 '18 at 6:13
Thanks Jeremy and sorry for the delay. Marked as answer!
– Dave
Dec 1 '18 at 6:13
Thanks Jeremy and sorry for the delay. Marked as answer!
– Dave
Dec 1 '18 at 6:13
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f53381140%2fadd-a-setting-to-app-config-or-will-adding-the-setting-to-exe-config-be-suffic%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
1
Hi Dave I spent a bit of time helping you out. If you have any questions let me know?
– Jeremy Thompson
Nov 30 '18 at 5:29
Thanks Jeremy! Very much appreciated.
– Dave
Dec 1 '18 at 6:14
Update for future readers.... In my case these fixes did not solve our intermittent scrollbar problems. We're still searching for the root cause (which could be hardware, drivers, etc. Not necessarily software). But I think we are now at least using Framework 4.7 and the potential fix correctly and can cross that off our list.
– Dave
Dec 1 '18 at 6:16