Mixing
Default Namespace Is Being Added to an Imported Library
I have create a custom control in a library in another project. I used a unique namespace i.e. MyNamespace.MyType
When I import the control into my main project I can see it in my toolbox. When I add the control, as per normal, by grabbing it in the toolbox and dragging it to my designer, afterwards in the code designer I get a red squiggly line and the error is 'MyNamespace.MyType' is not defined.
When I hover over the type in the code designer a tooltip pops up and inside it has the type name but it has also appended the main project's default namespace in front of MyNamespace.MyType that was created when I made the control in a separate project. I.e. it says 'DefaultNamespace.MyNamespace.Mytype'
I believe the issue with the squiggly line is that visual studio can't find the control (library) because it is using the DefaultNamespace.MyNamespace.MyType path.
When I hover over other Namespace.Mytype libraries in the code designer for the other controls and the popup window appears, the DefaultNamespace is not appended to the front of the controls namespace.mytype name for that library (and also no squiggly line either).
Also to test, I added the control into a seperate project file to see if I could duplicate this issue. However when I added the control I received no error and when I hovered over the type in the code designer, in the popup window the type name was not appended by the project's default namespace.
I will attach some screenshots of the popup window, with and without the default namespace appended to the front.
Has anyone seen this or has an opinion as to what is causing it?
visual-studio namespaces windows-forms-designer
asked Nov 21 '18 at 6:34
scott_fscott_f
562512
add a comment |
I have create a custom control in a library in another project. I used a unique namespace i.e. MyNamespace.MyType
When I import the control into my main project I can see it in my toolbox. When I add the control, as per normal, by grabbing it in the toolbox and dragging it to my designer, afterwards in the code designer I get a red squiggly line and the error is 'MyNamespace.MyType' is not defined.
When I hover over the type in the code designer a tooltip pops up and inside it has the type name but it has also appended the main project's default namespace in front of MyNamespace.MyType that was created when I made the control in a separate project. I.e. it says 'DefaultNamespace.MyNamespace.Mytype'
I believe the issue with the squiggly line is that visual studio can't find the control (library) because it is using the DefaultNamespace.MyNamespace.MyType path.
When I hover over other Namespace.Mytype libraries in the code designer for the other controls and the popup window appears, the DefaultNamespace is not appended to the front of the controls namespace.mytype name for that library (and also no squiggly line either).
Also to test, I added the control into a seperate project file to see if I could duplicate this issue. However when I added the control I received no error and when I hovered over the type in the code designer, in the popup window the type name was not appended by the project's default namespace.
I will attach some screenshots of the popup window, with and without the default namespace appended to the front.
Has anyone seen this or has an opinion as to what is causing it?
visual-studio namespaces windows-forms-designer
asked Nov 21 '18 at 6:34
scott_fscott_f
562512
add a comment |
I have create a custom control in a library in another project. I used a unique namespace i.e. MyNamespace.MyType
When I import the control into my main project I can see it in my toolbox. When I add the control, as per normal, by grabbing it in the toolbox and dragging it to my designer, afterwards in the code designer I get a red squiggly line and the error is 'MyNamespace.MyType' is not defined.
When I hover over the type in the code designer a tooltip pops up and inside it has the type name but it has also appended the main project's default namespace in front of MyNamespace.MyType that was created when I made the control in a separate project. I.e. it says 'DefaultNamespace.MyNamespace.Mytype'
I believe the issue with the squiggly line is that visual studio can't find the control (library) because it is using the DefaultNamespace.MyNamespace.MyType path.
When I hover over other Namespace.Mytype libraries in the code designer for the other controls and the popup window appears, the DefaultNamespace is not appended to the front of the controls namespace.mytype name for that library (and also no squiggly line either).
Also to test, I added the control into a seperate project file to see if I could duplicate this issue. However when I added the control I received no error and when I hovered over the type in the code designer, in the popup window the type name was not appended by the project's default namespace.
I will attach some screenshots of the popup window, with and without the default namespace appended to the front.
Has anyone seen this or has an opinion as to what is causing it?
visual-studio namespaces windows-forms-designer
asked Nov 21 '18 at 6:34
scott_fscott_f
562512
I have create a custom control in a library in another project. I used a unique namespace i.e. MyNamespace.MyType
When I import the control into my main project I can see it in my toolbox. When I add the control, as per normal, by grabbing it in the toolbox and dragging it to my designer, afterwards in the code designer I get a red squiggly line and the error is 'MyNamespace.MyType' is not defined.
When I hover over the type in the code designer a tooltip pops up and inside it has the type name but it has also appended the main project's default namespace in front of MyNamespace.MyType that was created when I made the control in a separate project. I.e. it says 'DefaultNamespace.MyNamespace.Mytype'
I believe the issue with the squiggly line is that visual studio can't find the control (library) because it is using the DefaultNamespace.MyNamespace.MyType path.
When I hover over other Namespace.Mytype libraries in the code designer for the other controls and the popup window appears, the DefaultNamespace is not appended to the front of the controls namespace.mytype name for that library (and also no squiggly line either).
Also to test, I added the control into a seperate project file to see if I could duplicate this issue. However when I added the control I received no error and when I hovered over the type in the code designer, in the popup window the type name was not appended by the project's default namespace.
I will attach some screenshots of the popup window, with and without the default namespace appended to the front.
Has anyone seen this or has an opinion as to what is causing it?
visual-studio namespaces windows-forms-designer
visual-studio namespaces windows-forms-designer
asked Nov 21 '18 at 6:34
scott_fscott_f
562512
asked Nov 21 '18 at 6:34
scott_fscott_f
562512
asked Nov 21 '18 at 6:34
scott_fscott_f
562512
asked Nov 21 '18 at 6:34
scott_fscott_f
562512
asked Nov 21 '18 at 6:34
scott_fscott_f
562512
562512
add a comment |
add a comment |
0
active
oldest
votes
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%2f53406445%2fdefault-namespace-is-being-added-to-an-imported-library%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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%2f53406445%2fdefault-namespace-is-being-added-to-an-imported-library%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
