How should be used these objects,
- do I have to create an object every time in an using block
(creating connection every time I need a query)
- I can create the object globally and reused for every query I need? Will the server close this connection if it is idle, and I will have an exception when trying to reuse it?
What do you mean by using delegates. To create some functions where I open the connection with using ?
Sorry, I didn't told the truth, I mixed it up with something completely different. The SqlConnection is threadsave. Therefore no delegates aren't needed. I used some other communication at the same time and this wasn't threadsafe, so delegates were needed.
I Develop an application with main form (MDI Form) and all child forms opened in the same form, but my problem is when open the application the windows task bar doesn't show until i minimize or close the application.
please help me if you can who to show the windows task bar in the same time when my application is opened.
If you have a Windows Form application here, it means one of two things - one, the taskbar is set to autohide, or two, you have code in the application that's designed to run the application full screen.
*pre-emptive celebratory nipple tassle jiggle* - Sean Ewington
Are you properly setting the MDiParent property of each child window to 'true ? Once you have set that property: the setting of 'ShowInTaskBar for MdiChild Forms has no effect.
See Pete O'Hanlon's reply above for other things you should check on.
And, also, if you are using Windows 7, there have been many bug reports to Microsoft about the Main TaskBar stuck on Visible, and not hiding, when its AutoHide property is set to false: I have this problem, at times myself, and have reported it: but I have never heard of anyone having a problem where the Main TaskBar was "stuck" on "closed."
<color>"When it comes to atoms, language can be used only as in poetry. The poet, too, is not nearly so concerned with describing facts as with creating images." Niels Bohr
Some One Plz Help Me
When i Am trying to Restore a database it gives me error-
System.Data.SqlClient.SqlException: Logical file DB_Jaggry isnot part ofdatabase DB_Jaggry_Restore&. UseRESTORE FILELISTONLY to list the logical file names.
RESTOREDATABASEis terminating abnormally
privatevoid button1_Click(object sender, EventArgs e)
Code fro Backup-
publicstaticvoid BackupDB(string backupDestinationFilePath)
// Console.WriteLine("Backup operation started");
Backup backup = new Backup();
//Set type of backup to be performed to database
backup.Action = BackupActionType.Database;
backup.BackupSetDescription = "BackupDataBase description";
//Set the name used to identify a particular backup set.
backup.BackupSetName = "Backup";
//specify the name of the database to back up
backup.Database = "DB_Jaggry";
//Set up the backup device to use filesystem.
BackupDeviceItem deviceItem = new BackupDeviceItem(
// Setup a new connection to the data server
ServerConnection connection = new ServerConnection();
Server sqlServer = new Server(@"SNEHA-PC\SQLEXPRESS");
//Initialize devices associated with a backup operation.
backup.Initialize = true;
backup.Checksum = true;
backup.ContinueAfterError = true;
backup.LogTruncation = BackupTruncateLogType.Truncate;
MessageBox.Show("Backup operation succeeded");
catch (Exception ex)
//Console.WriteLine("Backup operation failed");// Console.WriteLine(ex.Message);
Code For Restore-publicstaticvoid RestoreDB(string backUpFilePath, string databaseName)
Restore restore = new Restore();
restore.Database = databaseName;
restore.Action = RestoreActionType.Database;
restore.ReplaceDatabase = true;
restore.NoRecovery = false;
ServerConnection connection = new ServerConnection(@"SNEHA-PC\SQLEXPRESS");
Server sqlServer = new Server(connection);
MessageBox.Show("Restore operation succeeded");
catch (Exception ex)
Thnk u In Advance...
I’m working on a special project over the next 6 weeks while I recover from surgery. I’m trying to teach an old style C++ developer (me) new tricks using C#!
I’m looking for advice and some helpful links on how to convert a console based C++ program of mine to C#. I can go into the detail of the project, but it is fairly large and that would take us down the wrong path. I’m basically looking for some general information here.
My first thought on this is to create 3 separate solutions within one project.
The first would be a DLL that does all the work and returns the “feedback” (what it did and did it do successfully or have problems it had, etc.) back to the main process in the form of a string to be displayed.
I’ve never written a DLL, so this is a first for me also!
The second solution would be a windows form which can be used to set up the various calling parameters for calling the DLL to do its work …
And the third would be a console based application that would use the same DLL interface.
I’m using http://apex.vtc.com/ms-c-2008.php as a tutorial for learning C# and should be finished with the free stuff tomorrow at which time I will start paying my monthly fees until I have everything working properly. I’m using VS 2008 Professional Edition because that is what in loaded on my home PC.
Does this sound like a reasonable approach?
Where can I get a good tutorial on how to write a DLL and how to create bi-directional communicate with it?
Thanks in advance for any feedback and pointers you can offer.
I know it's probably more complicated than I understand, but to me a dll is just a library of functions that you add to your class with a using statement. In C# I believe you create it as a class library, then use the class member methods in your form or console app to accomplish useful things. Keep in mind, of course, that as a programmer I'm a complete idiot, barely functional, but I do manage to make things I need to have work somehow. I could be giving you bad advice, but it seems to me that you might want to create a class library to hold all the useful functions you use in multiple places, a Windows Form for the user interface, and a "something else" that actually controls all the interactions. The GUI part should really only handle display and input, then pass inputs to something else for handling, and respond to events for things that need to be displayed. Your class library would contain the functions that do all the heavy lifting.
In website development, there's a model called MVC - I don't know if it's applied to desktop apps, but I see no reason not to. I once reviewed a book on the subject, and got a free copy of the book when it was finally published, and I was much impressed by the logic of this approach. Your Model (M) would include the class library with all of the workhorse bits, the View (V) would just accept input and display results, and your Controller (C) would contain the state machine and event handlers that make everything happen. To my thinking, this would save you some work, as the command line version of your app could actually be the Controller, using a constructor that accepts the initial inputs on the command line, instead of being provided by your GUI interface. C# allows multiple constructors, so long as the signature is different for each, IIRC.
Of course, I could be leading you astray, being just a hobbyist who will never be an expert, as the majority of our members are. But that's the way I'd tackle it, then if I was completely wrong I'd come back here and beg for help. If it makes sense to you, give it a try... Good luck, and you might have the beginnings of a good article here. Keep that in mind...
using statements just allow you to elide the namespace name when you're typing a class name. To add a library to the available classes, you need to reference it: Add Reference to the project in an IDE, or use /r with csc.
You can create a dll by choosing Class Library in the project menu. Think of it as a group of namespaces or something, a whole set of functionality put together and that is reusable for other applications or other assemblies in your application.
However, a dll itself will not do something, you'll need an exe file which will be created if you choose the console or winforms/wpf projects, and then add a reference to use the dll. If you're totally new, start with a winforms and later move on the wpf.
For a first time I wouldn't search too far to hook up an application with an assembly, but basically there are three ways.
1. select one from your current solution
2. select one from the hard drive somewhere (optionally with a local copy or not)
3. If the assembly is added to the GAC, select it from there.
Just start out with 1.
You can also download VS2010 Express which is free (you'll need to register, but it's free) and SQL Server Express as well if you need it. (also free)
You can use MSDN[^] to find information on the objects and its members and this site [^] for more advanced help
Hope this helps somewhat, come back if you have specific questions.
I think you are looking at this from the wrong perspective. You have decided that you need a DLL without really understanding what a DLL is or how it would help to solve your problem. You say that you are converting a C++ console program to C#, so presumably the basics will be exactly the same, unless you are going for a completely new design. Look at your inputs, outputs and user interfaces first and decide how they should fit together. It may well be that a single executable written in C# will satisfy all the requirements.
One of these days I'm going to think of a really clever signature.