|
I'd try WMI and look for the MySQL service.
|
|
|
|
|
|
It's something like:
System.Management.ManagementScope oMs = new System.Management.ManagementScope(@"\\localhost");
oMs.Path.NamespacePath = @"root\cimv2";
string query = "select * From Win32_Service Where Name Like \"%mysql%\"";
System.Management.ObjectQuery oQuery = new System.Management.ObjectQuery(query);
ManagementObjectSearcher oSearcher = new ManagementObjectSearcher(oMs, oQuery);
ManagementObjectCollection oReturnCollection = oSearcher.Get();
foreach (ManagementObject oReturn in oReturnCollection)
{
foreach (PropertyData propertyData in oReturn.Properties)
{
txtResult.Text += string.Format("{0}: {1}\r\n", propertyData.Name, propertyData.Value);
}
}
This writes all information available on all services containing "mysql" in their name into textbox "txtResult".
Note also the "State" and "Started" properties.
|
|
|
|
|
sumit7034 wrote: I want to problematically determine...
really? 
it could be installed but not running, so maybe it is better to check for a process, with a name that contains "mysql"; the exact name may depend on the implementation, my XAMPP package launches a "mysqld" process.
See Process.GetProcessesByName()
|
|
|
|
|
Is it possible Inherit an internal class to a public class in C# class library
|
|
|
|
|
No. You can reduce accessibility, but you cannot increase it. Otherwise, what would be the point?
Real men don't use instructions. They are only the manufacturers opinion on how to put the thing together.
|
|
|
|
|
No. Why don't you try it?
Visual Studio will give you an "Inconsistent accessibility: base class xyz2 is less accessible than class xyz1" error when both classes are in the same source file.
|
|
|
|
|
thanx,
yup, i tried and got error msg.
Then pls let me know, what will be the use of internal class in class library(any real time eg)
mean signification reason of using internal class in class library
|
|
|
|
|
a class can be useful without being inherited; so could be a nested class, however an internal one is usable in several classes within the same source file.
|
|
|
|
|
|
That's not strictly true, Luc: internal classes are available within the same namespace rather than file. I frequently use internal for sub forms which are useful within the context of my public classes in a namespace, but which would be confusing or useless outside.
BTW: How did/is the chess go/going?
Real men don't use instructions. They are only the manufacturers opinion on how to put the thing together.
|
|
|
|
|
you are right, some people may put more than one namespace in a file, I know I wouldn't.
BTW: it is much too early to tell, preliminary battles yielded a typical 50%, however it is a 9-day open encounter according to the Swiss[^] pairing system.
|
|
|
|
|
Luc Pattyn wrote: some people may put more than one namespace in a file
Yeuch! No, no, no! Don't do it!
One class, one file.
One namespace, many files.
Internal is not restricted to file, just to namespace.
Real men don't use instructions. They are only the manufacturers opinion on how to put the thing together.
|
|
|
|
|
|
Assembly AND namespace. You cannot use someone else's internal classes by simply adding your own version of that namespace in your own assembly. The whole idea is to make it so that ONLY the guy who wrote the original method can decide how to use it. Not so that only people who know what namespace it is can use it. This is basic .net 101, and has been true since version 1.0.
edit: one more qualification, this applies to 'internal' classes that do not specify the 'internal' modifier. If you specify the 'internal' modifier you can use them within any namespace as long as you reference the correct one, but STILL only within the original assembly. So for example a class declared as
class MyClass(){ } can only be referenced in its original namespace and assembly.
However, one declared as
internal class MyClass() { } can be referenced by anything in the assembly.
|
|
|
|
|
Hang on, I've just realised - by file you are referring to Assembly (DLL/EXE) where I am referring to source. Oops!
But I agree - one assembly, one namespace.
Real men don't use instructions. They are only the manufacturers opinion on how to put the thing together.
|
|
|
|
|
you should have left it at that.
I did say source file, not assembly.
|
|
|
|
|
Internal class is visible only inside assembly. You can use it to implement functionality, that is required by your assembly, but shouldn't be accessible outside the assembly.
The real life example you say...
Let's say your application has an assembly for accessing database. You have classes with methods that perform some operations on database (insert, update, delete, select). Under the hood you use Entity Framework, but to assure, that database access is performed only with your classes, you set Entity Framework context class as internal. That provides you with cleaner code and strict separation of layers - higher layers don't know what mechanism you use for accessing database... and honestly, they shouldn't care.
Don't forget to rate answer, that helped you. It will allow other people find their answers faster.
|
|
|
|
|
If someone has a better idea in how I can do this please let me know. Normally I what I would do is call sqlreader and each field I would put into a custom array to use through out the application.
Well now that I have learned how to create a dataset, while in code without using the vs customized dataset's interface...
string connectionString = TheSQLConnectionString.ConnectionString.ToString();
using (connection = CreateConn())
{
command = new SqlCommand(TheSQLCommand, connection);
SqlDataAdapter adapter = new SqlDataAdapter(command);
adapter.Fill(dtSet);
}
Now what I want to be able to do is take the (dtSet) dataset and in code read each row and each row's columns of data.
However I want to place this code in a class Passing the parameters (table, row, and column) and I want the class procedure to return the value.
Can someone point me in the right direction please in how to understand datasets in order to accomplish this?
Thanks in advance.
|
|
|
|
|
If you don't actually want the DataSet, then don't create the DataSet.
I prefer to just use a DataReader and directly populate the classes I intend to use.
DataAdapters, DataSets, and DataGrid(View)s weren't created for actual real-world use -- their only purpose is allow MS demonstrators to quickly create barely-useful applications to make easily-impressed audiences go "ooohhh".
|
|
|
|
|
PIEBALDconsult wrote: DataAdapters, DataSets, and DataGrid(View)s weren't created for actual real-world use -- their only purpose is allow MS demonstrators to quickly create barely-useful applications to make easily-impressed audiences go "ooohhh".
10+
I bug
|
|
|
|
|
Ok how do you recommend getting the data from sql server database into the application if you do not recommend the use of datasets?
|
|
|
|
|
that question has been answered here already.
|
|
|
|
|
Motion Seconded, on all points.
ragnaroknrol The Internet is For Porn[^]
Pete o'Hanlon: If it wasn't insulting tools, I'd say you were dumber than a bag of spanners.
|
|
|
|
|
Cynical, definately cynical.
Never underestimate the power of human stupidity
RAH
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
