|
In c#, MessageBox.Show() should work. Check the case of the statement you have. C# is case sensitive.
Bhaskara
|
|
|
|
|
in c# message box is working. it is not a problem. im using it in class file..
|
|
|
|
|
You cannot have a messagebox displayed in a class file.
Bhaskara
|
|
|
|
|
What do you mean by saying that messagebox is not working?
|
|
|
|
|
if i type sqlconnection in my form it will shows the functions starts with letter "s"(sqlcommmand,sqladaptorm,reader) and sqlconnection also...
when i type messagebox.show the option messagebox.show did not displayed
|
|
|
|
|
In class library project, reference to System.Windows.Forms is not added. MessageBox is a class that is available in System.Windows.Forms namespace which is only added to the windows applications.
Bhaskara
|
|
|
|
|
SO the Intellisense is not working. Is the code compiling anyway?
One thing could be that you haven't included the namespace (System.Windows.Forms) in you file by using directive. Also the Intellisense may often get messed, but usually restarting the development environment corrects that. If that doesn't help, you could set the intellisense off from options, restart visual studio and set it on again.
Also check that you have service packs installed for visual studio.
|
|
|
|
|
both of u got that
am not included the namespace
|
|
|
|
|
I didn't quite understand you reply, but if you haven't included the namespace, add
using System.Windows.Forms;
to the beginning of your file
|
|
|
|
|
added and executed successfully...
thx..
|
|
|
|
|
|
MessageBox.Show("your message goes here");
|
|
|
|
|
Since a class file shouldn't show any kind of user interface, you don't do this.
|
|
|
|
|
how to display user control in windows form i've multiple user control and i'm trying to display usercontrol individualy
please help me to solve this problem. 
|
|
|
|
|
you can use use this.controls.add(this.usercontrolname) to dynamically add the usercontrol to the forms control collection. (use Me if you are doing it in vb.net)
Bhaskara
|
|
|
|
|
Hi Friends,
Can any body help me what is the best method parse large XML File having size of 1GB.If i use XML Document and XML Reader ,result being very late....
Your answers are welcme
Thanks with best regards,
sivaram
|
|
|
|
|
For XML files of that size, XMLDocument or DOM is not suitable. XMLReader should give better performance than the former one.
In case if you are using string manipulations, consider StringBuilder object also in place String. (Just a thought)
Bhaskara
|
|
|
|
|
If you use the XML libraries in C# does it not work for your large file? I've never tried anything with a file that big.
ɹǝʌo ɹoʇıuoɯ ɹnoʎ dılɟ sıɥʇ pɐǝɹ ʇ,uɐɔ noʎ ɟı
|
|
|
|
|
I rad about how the garbage collector work.
From what i rad is that any value type variable can't be application root item - so the value type is can't be collect by the garbage collector ?
If not - how the garbage collector collect value type objects ?
|
|
|
|
|
"I read"...not "I rad"...
Value types are allocated on the stack by default, so they don't need to be managed by the GC. Stack objects are discarded whenever that stack frame ends and is popped, which is a fundamental aspect of any program, regardless of whether there is a GC or not.
|
|
|
|
|
Thanks!
just forgot the "e" ... in the read / rad
|
|
|
|
|
Jon Rista wrote: Value types are allocated on the stack by default,
IMO there is no default, i.e. value types are allocated on the stack when they are local variables, and inside their containing type when they are members of an aggregated type (hence
on the heap when members of a class, and where ever it resides when members of a struct).
In each case, there is no explicit garbage collection involved: in the end they reside either on
the stack (hence no garbage collection at all) or are part of a bigger reference type (and collection occurs at that ref type level).
|
|
|
|
|
Well, sure. I wouldn't consider a field in a class as an isolated thing...its an integral part of the class. I think the gyst of the question was "Why isn't an int allocated on the heap and GCed by default". :P
|
|
|
|
|
I think the gyst of the question was "Why isn't an int allocated on the heap and GCed by default".
Non-static class fields are stored on the heap within the memory areas that are allocated to objects. They go bye-bye if the objects containing them are garbage-collected. I believe static fields are stored on the heap as well, but in regions that generally won't go bye-bye until an application terminates (I think there are ways of explicitly unloading DLL's which would nuke any static fields they hold, but I don't know the details).
As noted before, local variables are stored on the stack, and will go bye-bye when, or soon after, they go out of scope.
Note that class variables hold references to objects; the class variables themselves are value types (which may be stored on the stack or within the space allocated for particular objects), but they will cause the system to maintain objects as standalone allocations.
Thus, if there is a local variable of type "System.Text.Stringbuilder", the local variable will exist on the stack only as long as it is within scope. If the variable is not Nothing, there will be an object of type System.Text.Stringbuilder to which that variable points. When the variable goes out of scope, the four or eight bytes used by the reference itself will go away regardless of whether other references exist to the same StringBuilder.
|
|
|
|
|
Static types and fields are stored in what is called a Loader Heap. Loader heaps are separate from the normal GC heap, and are managed in a different way. They are not garbage collected (since they are static and live for the duration of the app, there is no need), and space for statics is preallocated when the AppDomain is loaded. If a Static member contains a reference to another, non-static object...the object that is referenced is actually stored on the GC heap. Static fields and methods are keept on loader heaps because they are considered part of the type system (wich is the primary purpose for loader heaps...to store type metadata, vtables, etc.) Its actually an interesting distinction between static and instance types.
Given that this thread has diverged from simple answers, perhapse the following link will be helpful to everyone. It explains the CLR, GC, and type system in detail:
http://msdn.microsoft.com/en-us/magazine/cc163791.aspx
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
