Force update in InitializeComponent
0
I'm deveoloping in VB.Net and I'm making batch modification to Designer.vb file. My new code compiles, but there are some modification that does not apply until I open the Designer.vb in Design mode in the VS.
When I open it in VS, the Windows Form Designer rewrite InitializeComponent and the Designer works fine.
Is there any way I can make a batch to force the Windows Form Designer to "rebuild" or "update" my new code, so it's get ok?
Thanks in advance!
vb.net designer vb6-migration
asked Nov 21 '18 at 13:02
Diego FerreroDiego Ferrero
111
add a comment |
0
I'm deveoloping in VB.Net and I'm making batch modification to Designer.vb file. My new code compiles, but there are some modification that does not apply until I open the Designer.vb in Design mode in the VS.
When I open it in VS, the Windows Form Designer rewrite InitializeComponent and the Designer works fine.
Is there any way I can make a batch to force the Windows Form Designer to "rebuild" or "update" my new code, so it's get ok?
Thanks in advance!
vb.net designer vb6-migration
asked Nov 21 '18 at 13:02
Diego FerreroDiego Ferrero
111
"batch modification" are two very scary words. VS has no reason to assume that anything changed behind its back when the form is opened in the designer. You must close the designer first to avoid accidents.
– Hans Passant
Nov 21 '18 at 13:11
Please verify the steps. 1) External to VS, the <form>.designer.vb file is modified. 2) the modified code compiles; however, the executable does not appear as desired. 3) You open the project in VS and open the form in design view. 4) the form designer updates the <form>.designer.vb file such that when compiled the executable appears as wanted. If this is accurate, then I suspect that you are adding a component to the InitializeComponent method but are not including the all the initialization code added by its CodeDomSerializer. Figure out the missing statements and add them to step 1.
– TnTinMn
Nov 21 '18 at 14:00
If the pattern of what it changes inInitializeComponent is consistent, you could / should try to manually replicate this. Also, I would be sure to use source control between each revision to these files to save trouble if/when things go wrong!
– DaveInCaz
Nov 26 '18 at 12:42
add a comment |
0
0
0
I'm deveoloping in VB.Net and I'm making batch modification to Designer.vb file. My new code compiles, but there are some modification that does not apply until I open the Designer.vb in Design mode in the VS.
When I open it in VS, the Windows Form Designer rewrite InitializeComponent and the Designer works fine.
Is there any way I can make a batch to force the Windows Form Designer to "rebuild" or "update" my new code, so it's get ok?
Thanks in advance!
vb.net designer vb6-migration
asked Nov 21 '18 at 13:02
Diego FerreroDiego Ferrero
111
I'm deveoloping in VB.Net and I'm making batch modification to Designer.vb file. My new code compiles, but there are some modification that does not apply until I open the Designer.vb in Design mode in the VS.
When I open it in VS, the Windows Form Designer rewrite InitializeComponent and the Designer works fine.
Is there any way I can make a batch to force the Windows Form Designer to "rebuild" or "update" my new code, so it's get ok?
Thanks in advance!
vb.net designer vb6-migration
vb.net designer vb6-migration
asked Nov 21 '18 at 13:02
Diego FerreroDiego Ferrero
111
asked Nov 21 '18 at 13:02
Diego FerreroDiego Ferrero
111
asked Nov 21 '18 at 13:02
Diego FerreroDiego Ferrero
111
asked Nov 21 '18 at 13:02
Diego FerreroDiego Ferrero
111
asked Nov 21 '18 at 13:02
Diego FerreroDiego Ferrero
111
111
"batch modification" are two very scary words. VS has no reason to assume that anything changed behind its back when the form is opened in the designer. You must close the designer first to avoid accidents.
– Hans Passant
Nov 21 '18 at 13:11
Please verify the steps. 1) External to VS, the <form>.designer.vb file is modified. 2) the modified code compiles; however, the executable does not appear as desired. 3) You open the project in VS and open the form in design view. 4) the form designer updates the <form>.designer.vb file such that when compiled the executable appears as wanted. If this is accurate, then I suspect that you are adding a component to the InitializeComponent method but are not including the all the initialization code added by its CodeDomSerializer. Figure out the missing statements and add them to step 1.
– TnTinMn
Nov 21 '18 at 14:00
If the pattern of what it changes inInitializeComponent is consistent, you could / should try to manually replicate this. Also, I would be sure to use source control between each revision to these files to save trouble if/when things go wrong!
– DaveInCaz
Nov 26 '18 at 12:42
add a comment |
"batch modification" are two very scary words. VS has no reason to assume that anything changed behind its back when the form is opened in the designer. You must close the designer first to avoid accidents.
– Hans Passant
Nov 21 '18 at 13:11
Please verify the steps. 1) External to VS, the <form>.designer.vb file is modified. 2) the modified code compiles; however, the executable does not appear as desired. 3) You open the project in VS and open the form in design view. 4) the form designer updates the <form>.designer.vb file such that when compiled the executable appears as wanted. If this is accurate, then I suspect that you are adding a component to the InitializeComponent method but are not including the all the initialization code added by its CodeDomSerializer. Figure out the missing statements and add them to step 1.
– TnTinMn
Nov 21 '18 at 14:00
If the pattern of what it changes inInitializeComponent is consistent, you could / should try to manually replicate this. Also, I would be sure to use source control between each revision to these files to save trouble if/when things go wrong!
– DaveInCaz
Nov 26 '18 at 12:42
"batch modification" are two very scary words. VS has no reason to assume that anything changed behind its back when the form is opened in the designer. You must close the designer first to avoid accidents.
– Hans Passant
Nov 21 '18 at 13:11
"batch modification" are two very scary words. VS has no reason to assume that anything changed behind its back when the form is opened in the designer. You must close the designer first to avoid accidents.
– Hans Passant
Nov 21 '18 at 13:11
Please verify the steps. 1) External to VS, the <form>.designer.vb file is modified. 2) the modified code compiles; however, the executable does not appear as desired. 3) You open the project in VS and open the form in design view. 4) the form designer updates the <form>.designer.vb file such that when compiled the executable appears as wanted. If this is accurate, then I suspect that you are adding a component to the InitializeComponent method but are not including the all the initialization code added by its CodeDomSerializer. Figure out the missing statements and add them to step 1.
– TnTinMn
Nov 21 '18 at 14:00
Please verify the steps. 1) External to VS, the <form>.designer.vb file is modified. 2) the modified code compiles; however, the executable does not appear as desired. 3) You open the project in VS and open the form in design view. 4) the form designer updates the <form>.designer.vb file such that when compiled the executable appears as wanted. If this is accurate, then I suspect that you are adding a component to the InitializeComponent method but are not including the all the initialization code added by its CodeDomSerializer. Figure out the missing statements and add them to step 1.
– TnTinMn
Nov 21 '18 at 14:00
If the pattern of what it changes inInitializeComponent is consistent, you could / should try to manually replicate this. Also, I would be sure to use source control between each revision to these files to save trouble if/when things go wrong!
– DaveInCaz
Nov 26 '18 at 12:42
If the pattern of what it changes inInitializeComponent is consistent, you could / should try to manually replicate this. Also, I would be sure to use source control between each revision to these files to save trouble if/when things go wrong!
– DaveInCaz
Nov 26 '18 at 12:42
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
});
}
});
draft saved
draft discarded
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%2f53412639%2fforce-update-in-initializecomponent%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
draft saved
draft discarded
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.
draft saved
draft discarded
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%2f53412639%2fforce-update-in-initializecomponent%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
"batch modification" are two very scary words. VS has no reason to assume that anything changed behind its back when the form is opened in the designer. You must close the designer first to avoid accidents.
– Hans Passant
Nov 21 '18 at 13:11
Please verify the steps. 1) External to VS, the <form>.designer.vb file is modified. 2) the modified code compiles; however, the executable does not appear as desired. 3) You open the project in VS and open the form in design view. 4) the form designer updates the <form>.designer.vb file such that when compiled the executable appears as wanted. If this is accurate, then I suspect that you are adding a component to the InitializeComponent method but are not including the all the initialization code added by its CodeDomSerializer. Figure out the missing statements and add them to step 1.
– TnTinMn
Nov 21 '18 at 14:00
If the pattern of what it changes inInitializeComponent is consistent, you could / should try to manually replicate this. Also, I would be sure to use source control between each revision to these files to save trouble if/when things go wrong!
– DaveInCaz
Nov 26 '18 at 12:42