|
i have a problem in my code for doing the slectedindex event.pls help
SqlCommand cmd = new SqlCommand("select firstname,phoneno from user1 where rollno='" + comboBox1.SelectedItem + "'", con);
SqlDataReader dr;
con.Open();
dr = cmd.ExecuteReader();
if (dr.Read())
{
textBox1.Text = dr[0].ToString();
textBox2.Text = dr[1].ToString();
label4.Visible = true;
label4.Text = "show";
}
con.Close();
|
|
|
|
|
What error are you getting ?
When I was a coder, we worked on algorithms. Today, we memorize APIs for countless libraries — those libraries have the algorithms - Eric Allman
|
|
|
|
|
Null Reference Exception?
When you select a different value in a ComboBox, the previous element gets de-selected, causing a SelectedIndexChanged event. Now, nothing is selected, the SelectedIndex is -1. Next, the element you selected gets selected, causing the next SelectedIndexChanged event. And now it is really selected, and you can use it.
|
|
|
|
|
Hi
I want to use windows login box in my c# application which is secure and pass values using tokens. I do not want to create a custom login box. How to popup the login screen?
Thanks in advance,
Sai
|
|
|
|
|
|
Thank you very much  ...
|
|
|
|
|
|
Is this a custom built? I do not want to use custom built. I did one myself using Active directory directory service reference and the company do not want it.
Thank you,
Sai
|
|
|
|
|
I have a web service stack trace where the method is called GetLoadTrace();
However, I can't seem to find what line the error occured in . Does the stack trace tell you ?
It just says GetLoadTrace()+90
GetLoadTrace()+155
What line did the error occur on then ? Does it NOT tell you ?
==================================================
--I am the STIG !!!!!!!!!!!!!!!!!
|
|
|
|
|
The exception is usually thrown in the method at the very top of the stack trace.
The stack trace does NOT tell you on which line the problem occured in a Release compiled application, only the method in which it occured.
|
|
|
|
|
It's not actually release/debug, it's whether a .pdb file is present ... but I don't think it's possible to make a .pdb for a release build so you can never get line numbers in a release stack trace.
|
|
|
|
|
BobJanova wrote: I don't think it's possible to make a .pdb
You can. A release build is not magic, the main difference is just that the debug version doesn't optimise the code. If you do a release build, take a look in your Release folder - you'll see a number of generated PDB files in there.
To prevent generation of release PDV files, select Project Properties > Build > Advanced > Debug Info: None (make sure the configration is set to Release when you do this).
|
|
|
|
|
Oh, I thought that the optimisations made it too hard for the compiler to know what to create.
If I'm using csc, and I use /debug to create a .pdb, then, is that still 'release' code (i.e. optimised etc)?
|
|
|
|
|
It's not release code if you use csc /debug. If you want to do the release build that you get with Visual Studio, just use csc.exe /optimize+ /debug:pdbonly. To just produce the release build without the pdb, just use csc.exe /optimize+.
|
|
|
|
|
The compiler will know what to create easy enough.
My problem is with optimizations and code rewrite, are the line numbers going to be accurate??
|
|
|
|
|
I need to create a help file for an application. Not code comments but actual "how to use" help file for end users.
Which "tool" should I use?
Which tool have you used? Did you think it was good? Why?
Which tool shouldnt I use? Why not?
Thanks
bart
|
|
|
|
|
This isn't really an appropriate question for the C# forum. What you could do is download and test some of the help authoring tools to see which best suits your requirements.
|
|
|
|
|
Can you suggest a better forum?
bart
|
|
|
|
|
Possibly the lounge. And rather than post your question like this, I'd rephrase it to be a more general "does anyone have any experience with help authoring tools? I'm interested in which tools people have used to write documentation for end users, rather than API style documentation, and how they found them."
|
|
|
|
|
so you will answer in the lounge? Without any elephants?
bart
|
|
|
|
|
Some might - when you post, put in that I suggested that you posted there.
|
|
|
|
|
Good point.
We "use" Microsoft HTML Help Workshop 1.3 - it's old, and it's not good to use. (And we hardly ever use it, our help files are really outdated).
At a different company, the documentation guys used RoboHelp. It allowed for better help integration than the HTML Workshop, you could generate context-sensitive help downto the controls on a form. But I do not know how hard it is to use.
|
|
|
|
|
These days I just create HTML pages and have the F1 link point a browser at it. The classic .hlp type help is no longer supported under recent Windows, and .chm help is just HTML but annoying to use.
|
|
|
|
|
My project was created in winxp and now migrated to windows7. I am getting a weird exception while click on the openfiledialog icon in my project and the application crashes after this. This only happens when I create a release build and install that build in windows 7.
The setup is also created in the windows 7. I do no get this exception when run the code in the debug mode.
I am setting the initialdirectory property of the openfiledialog to desktopdirectory.
Below is the exception trace i caught in the windows event viewer.
Application: projectname.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
Stack:
at System.Windows.Forms.UnsafeNativeMethods.GetOpenFileName(OPENFILENAME_I)
at System.Windows.Forms.OpenFileDialog.RunFileDialog(OPENFILENAME_I)
at System.Windows.Forms.FileDialog.RunDialogOld(IntPtr)
at System.Windows.Forms.FileDialog.RunDialog(IntPtr)
at System.Windows.Forms.CommonDialog.ShowDialog(System.Windows.Forms.IWin32Window)
at System.Windows.Forms.CommonDialog.ShowDialog()
at companyname.projectname.MainForm.processFileOperation(FileOperationType)
at companyname.projectname.MainForm.fileOpenMenuItem_Click(System.Object, System.EventArgs)
at companyname.projectname.MainForm.toolBar_ButtonClick(System.Object, System.Windows.Forms.ToolBarButtonClickEventArgs)
at System.Windows.Forms.ToolBar.OnButtonClick(System.Windows.Forms.ToolBarButtonClickEventArgs)
at System.Windows.Forms.ToolBar.WmReflectCommand(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.ToolBar.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.Control+ControlNativeWindow.OnMessage(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.Control+ControlNativeWindow.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.NativeWindow.Callback(IntPtr, Int32, IntPtr, IntPtr)
at System.Windows.Forms.UnsafeNativeMethods.SendMessage(System.Runtime.InteropServices.HandleRef, Int32, IntPtr, IntPtr)
at System.Windows.Forms.Control.SendMessage(Int32, IntPtr, IntPtr)
at System.Windows.Forms.Control.ReflectMessageInternal(IntPtr, System.Windows.Forms.Message ByRef)
at System.Windows.Forms.Control.WmCommand(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.Control.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.ScrollableControl.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.Form.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.Control+ControlNativeWindow.OnMessage(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.Control+ControlNativeWindow.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.NativeWindow.Callback(IntPtr, Int32, IntPtr, IntPtr)
at System.Windows.Forms.UnsafeNativeMethods.CallWindowProc(IntPtr, IntPtr, Int32, IntPtr, IntPtr)
at System.Windows.Forms.NativeWindow.DefWndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.Control.DefWndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.Control.WmMouseUp(System.Windows.Forms.Message ByRef, System.Windows.Forms.MouseButtons, Int32)
at System.Windows.Forms.Control.WndProc
(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.ToolBar.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.Control+ControlNativeWindow.OnMessage(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.Control+ControlNativeWindow.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.NativeWindow.Callback(IntPtr, Int32, IntPtr, IntPtr)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG ByRef)
at System.Windows.Forms.Application
+ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr, Int32, Int32)
at System.Windows.Forms.Application+ThreadContext.RunMessageLoopInner(Int32, System.Windows.Forms.ApplicationContext)
at System.Windows.Forms.Application+ThreadContext.RunMessageLoop(Int32, System.Windows.Forms.ApplicationContext)
at System.Windows.Forms.Application.Run(System.Windows.Forms.Form)
at companyname.projectname.MainForm.Main(System.String[])
|
|
|
|
|
This is not caused by a building a release-mode or creatng a setup on Windows 7. First, you'll need to implement an event[^] to deal with "unhandled exceptions". Next, you'd need to debug to find out the cause of the exception; my guess is that the filename or the path is mukking up things.
Can you post the code that calls your dialog? And the filename/path that you select? And the initial directory you try to set?
Bastard Programmer from Hell 
if you can't read my code, try converting it here[^]
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
