WPF Restrict ResourceDictionary to assembly
I am using C# 4.7.2 and WPF 4.5
I want register resources that defined in a specific assembly to be registered explicitly in the defining assembly. The application is exensible and I'm looking for a way to avoid name duplicates and the erros thrown as a result to them.
Is it possible to restricht the scope for resources? Does anybody know a way, to use names for dictionaries?
I'v tried a derivation from ResourceDictionary. But this derivation isn't accepted as parameter to
System.Windows.Application.Current.Resources.MergedDictionaries.Add
c# wpf resources
asked Nov 23 '18 at 11:12
GeorgeDukeGeorgeDuke
76
add a comment |
I am using C# 4.7.2 and WPF 4.5
I want register resources that defined in a specific assembly to be registered explicitly in the defining assembly. The application is exensible and I'm looking for a way to avoid name duplicates and the erros thrown as a result to them.
Is it possible to restricht the scope for resources? Does anybody know a way, to use names for dictionaries?
I'v tried a derivation from ResourceDictionary. But this derivation isn't accepted as parameter to
System.Windows.Application.Current.Resources.MergedDictionaries.Add
c# wpf resources
asked Nov 23 '18 at 11:12
GeorgeDukeGeorgeDuke
76
add a comment |
I am using C# 4.7.2 and WPF 4.5
I want register resources that defined in a specific assembly to be registered explicitly in the defining assembly. The application is exensible and I'm looking for a way to avoid name duplicates and the erros thrown as a result to them.
Is it possible to restricht the scope for resources? Does anybody know a way, to use names for dictionaries?
I'v tried a derivation from ResourceDictionary. But this derivation isn't accepted as parameter to
System.Windows.Application.Current.Resources.MergedDictionaries.Add
c# wpf resources
asked Nov 23 '18 at 11:12
GeorgeDukeGeorgeDuke
76
I am using C# 4.7.2 and WPF 4.5
I want register resources that defined in a specific assembly to be registered explicitly in the defining assembly. The application is exensible and I'm looking for a way to avoid name duplicates and the erros thrown as a result to them.
Is it possible to restricht the scope for resources? Does anybody know a way, to use names for dictionaries?
I'v tried a derivation from ResourceDictionary. But this derivation isn't accepted as parameter to
System.Windows.Application.Current.Resources.MergedDictionaries.Add
c# wpf resources
c# wpf resources
asked Nov 23 '18 at 11:12
GeorgeDukeGeorgeDuke
76
asked Nov 23 '18 at 11:12
GeorgeDukeGeorgeDuke
76
asked Nov 23 '18 at 11:12
GeorgeDukeGeorgeDuke
76
asked Nov 23 '18 at 11:12
GeorgeDukeGeorgeDuke
76
asked Nov 23 '18 at 11:12
GeorgeDukeGeorgeDuke
76
76
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
When you merge a resource you do so with a scope.
Application.current.resources is where stuff you merge in app.xaml goes.
Below that... you have control scope.
A project / dll which you reference loads into the application's scope ( simplifying ). So you would need each view or whatever in that dll to load an instance of your resource dictionary. Which could of course have significant overhead.
A simple work round would be to have a prefix on the x:Key of your resources which is unique to each assembly.
answered Nov 23 '18 at 16:35
AndyAndy
2,9701106
Thanks Andy. But I'm afraid the scope is ALWAYS the executing assembly. In my case, the resources are located in a satellite library, which is unkown to the executing Assembly. The scope of the satellite resources is the executing assembly - proven. I am aware of qualified names, but I am trying different approaches, as well.
– GeorgeDuke
Nov 23 '18 at 20:23
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%2f53445619%2fwpf-restrict-resourcedictionary-to-assembly%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
When you merge a resource you do so with a scope.
Application.current.resources is where stuff you merge in app.xaml goes.
Below that... you have control scope.
A project / dll which you reference loads into the application's scope ( simplifying ). So you would need each view or whatever in that dll to load an instance of your resource dictionary. Which could of course have significant overhead.
A simple work round would be to have a prefix on the x:Key of your resources which is unique to each assembly.
answered Nov 23 '18 at 16:35
AndyAndy
2,9701106
Thanks Andy. But I'm afraid the scope is ALWAYS the executing assembly. In my case, the resources are located in a satellite library, which is unkown to the executing Assembly. The scope of the satellite resources is the executing assembly - proven. I am aware of qualified names, but I am trying different approaches, as well.
– GeorgeDuke
Nov 23 '18 at 20:23
add a comment |
When you merge a resource you do so with a scope.
Application.current.resources is where stuff you merge in app.xaml goes.
Below that... you have control scope.
A project / dll which you reference loads into the application's scope ( simplifying ). So you would need each view or whatever in that dll to load an instance of your resource dictionary. Which could of course have significant overhead.
A simple work round would be to have a prefix on the x:Key of your resources which is unique to each assembly.
answered Nov 23 '18 at 16:35
AndyAndy
2,9701106
Thanks Andy. But I'm afraid the scope is ALWAYS the executing assembly. In my case, the resources are located in a satellite library, which is unkown to the executing Assembly. The scope of the satellite resources is the executing assembly - proven. I am aware of qualified names, but I am trying different approaches, as well.
– GeorgeDuke
Nov 23 '18 at 20:23
add a comment |
When you merge a resource you do so with a scope.
Application.current.resources is where stuff you merge in app.xaml goes.
Below that... you have control scope.
A project / dll which you reference loads into the application's scope ( simplifying ). So you would need each view or whatever in that dll to load an instance of your resource dictionary. Which could of course have significant overhead.
A simple work round would be to have a prefix on the x:Key of your resources which is unique to each assembly.
answered Nov 23 '18 at 16:35
AndyAndy
2,9701106
When you merge a resource you do so with a scope.
Application.current.resources is where stuff you merge in app.xaml goes.
Below that... you have control scope.
A project / dll which you reference loads into the application's scope ( simplifying ). So you would need each view or whatever in that dll to load an instance of your resource dictionary. Which could of course have significant overhead.
A simple work round would be to have a prefix on the x:Key of your resources which is unique to each assembly.
answered Nov 23 '18 at 16:35
AndyAndy
2,9701106
answered Nov 23 '18 at 16:35
AndyAndy
2,9701106
answered Nov 23 '18 at 16:35
AndyAndy
2,9701106
answered Nov 23 '18 at 16:35
AndyAndy
2,9701106
2,9701106
Thanks Andy. But I'm afraid the scope is ALWAYS the executing assembly. In my case, the resources are located in a satellite library, which is unkown to the executing Assembly. The scope of the satellite resources is the executing assembly - proven. I am aware of qualified names, but I am trying different approaches, as well.
– GeorgeDuke
Nov 23 '18 at 20:23
add a comment |
Thanks Andy. But I'm afraid the scope is ALWAYS the executing assembly. In my case, the resources are located in a satellite library, which is unkown to the executing Assembly. The scope of the satellite resources is the executing assembly - proven. I am aware of qualified names, but I am trying different approaches, as well.
– GeorgeDuke
Nov 23 '18 at 20:23
Thanks Andy. But I'm afraid the scope is ALWAYS the executing assembly. In my case, the resources are located in a satellite library, which is unkown to the executing Assembly. The scope of the satellite resources is the executing assembly - proven. I am aware of qualified names, but I am trying different approaches, as well.
– GeorgeDuke
Nov 23 '18 at 20:23
Thanks Andy. But I'm afraid the scope is ALWAYS the executing assembly. In my case, the resources are located in a satellite library, which is unkown to the executing Assembly. The scope of the satellite resources is the executing assembly - proven. I am aware of qualified names, but I am trying different approaches, as well.
– GeorgeDuke
Nov 23 '18 at 20:23
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%2f53445619%2fwpf-restrict-resourcedictionary-to-assembly%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
