For those new to message boards please try to follow a few simple rules when posting your question.
Choose the correct forum for your message. Posting a VB.NET question in the C++ forum will end in tears.
Be specific! Don't ask "can someone send me the code to create an application that does 'X'. Pinpoint exactly what it is you need help with.
Keep the subject line brief, but descriptive. eg "File Serialization problem"
Keep the question as brief as possible. If you have to include code, include the smallest snippet of code you can.
Be careful when including code that you haven't made a typo. Typing mistakes can become the focal point instead of the actual question you asked.
Do not remove or empty a message if others have replied. Keep the thread intact and available for others to search and read. If your problem was answered then edit your message and add "[Solved]" to the subject line of the original post, and cast an approval vote to the one or several answers that really helped you.
If you are posting source code with your question, place it inside <pre></pre> tags. We advise you also check the "Encode "<" (and other HTML) characters when pasting" checkbox before pasting anything inside the PRE block, and make sure "Use HTML in this post" check box is checked.
Be courteous and DON'T SHOUT. Everyone here helps because they enjoy helping others, not because it's their job.
Please do not post links to your question into an unrelated forum such as the lounge. It will be deleted. Likewise, do not post the same question in more than one forum.
Do not be abusive, offensive, inappropriate or harass anyone on the boards. Doing so will get you kicked off and banned. Play nice.
If you have a school or university assignment, assume that your teacher or lecturer is also reading these forums.
No advertising or soliciting.
We reserve the right to move your posts to a more appropriate forum or to delete anything deemed inappropriate or illegal.
Apologies if this is in the wrong section, I recently tried to install an application on my personal computer & received the following message - I have also proven the installer as it worked perfectly on my wife's computer.
Any Help you could provide would be very much appriciated.
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.ComponentModel.Win32Exception (0x80004005): The system cannot find the file specified
at DigiCheck.Form1.ProcExec(String command, String options)
at DigiCheck.Form1.Form1_Shown(Object sender, EventArgs e)
at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme)
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
I recently found this article Writing Reliable .NET Code[^] and I'm very interested in the topic but for my taste it's a too high altitude flyover. Google wasn't able or not willing to show me articles that cover the exact same topic but are a bit more hands-on. Does anyone have some pointers for me?
So, Im writing a Forms application, an I am using the Validating event on some TextBoxes (setting e.Cancel = true if bad input). It works just fine until I click the red x in order to exit the application. If a textbox with faulty text has the focus then, the Validating event runs and makes the application not exit. What can I do about it?
Thanks, that article is exactly what I experience. Though the trick with the FormClosing event didnt really do it for me. The application does exit, but not until my MessageBox is sprung from the Validating event.
What did work the way I intended (the application exiting without any validating), was the WndProc override.
privateconstint WM_CLOSE = 0x0010;
protectedoverridevoid WndProc(ref Message m)
if (m.Msg == WM_CLOSE) // Attempting to close Form
AutoValidate = AutoValidate.Disable; //this stops (all) validations
base.WndProc(ref m); //call the base method to handle other messages
two days age i start visual basic.net and i know basic syntax of java and c++ very well now i want to see whole classes and methods of .NET Framework class libraries same like the documentation of java language so help me how to download the documentation
Visual Studio 2010 VB using the VS Setup and Deploy to create an MSI install file.
2 Similar programs uninstalling each other.
We had a program running for a few years. We needed a similar program so we decided to use it a base. So The Program 1 folder was copied to create the Program 2 folder. Renames were done on the folder names and main modules. SLN file changed. The GUID in the Assembly info was changed.
We can install either but when we install program 2 from the IDE it first uninstalls program 1. Same when we install Program 1 it uninstalls program 2.
When we install them they both appear with the correct name in Control Panel programs but one or the other.
I understand something got crossed but what?
How can we fix it?
Most likely the Product Code got duplicated from the first to the second setup. Each installer must have a unique Product Code which is a GUID.
I can't help you find it in Visual Studio, though, because I never use those setup projects. I use InstallShield.
Try looking for the Product Code and change it in the second setup.
NOTE: The Upgrade Code must also be unique for a separate product installer. If product 2 is only an upgrade of product 1, then the Upgrade Codes should be the same, otherwise they should be different.
The difficult we do right away...
...the impossible takes slightly longer.