So? You have the individual menustrip item click event, which tells you the user wants to do something, and what he wants to do. And you have the DataGridView click event which tells you that the user has left - or right - clicked and on which DataGridView he clicked.
Put the two together and something magical may occur...
Did you know:
That by counting the rings on a tree trunk, you can tell how many other trees it has slept with.
I have an application in C# that use SQL Server 2008 R2 Express.
When i install the package i need to choose option and to install:
1. Microsoft .Net Framework 3.5 SP1.
2. Windows Installer 4.5.
3. Windows PowerShell 1.0
I have an SQL Script that will build my DB at SQL 2008 R2 Express and will add the user configuration that i want.
I want to make install package that will include the SQL 2008 R2 Express (including "Microsoft .Net Framework 3.5 SP1.",
,"Windows Installer 4.5" and "Windows PowerShell 1.0 ").
Will run the script and install my application.
I don't want to let the user to choose configuration for the DB in the installation process.
How can i do that?
My preference, and I think there are others here who agree, is to not try to do that.
Simply document the system requirements of the application and let the user install what's needed however they like.
Think of it this way... what if your install installs today's current features, but a user wants to install it sometime in the future and doesn't want to install "old" versions of this stuff.
Plus, the user may already have the stuff you require installed (or better). Why install SQL Server Express when the user already has the full package?
Or maybe the user wants to have SQL Server on a server (where it belongs), not on his workstation?
Your install should install your application and nothing else.
Indeed, don't force your customer to install sql express. I agree to PIEBALDconsult post.
Maybe its the easiest way to create your installation, but its the wrong way. Your installation should get the required data (connection settings etc.), check the connection, then it should install the database. If the connection fails, cancel the setup.
I have been using this code for a while now and it has been working well. I have just switched to Windows 7 and was starting a new project to create a service configuration and installation tool. I reused this code and it fails on Windows 7. The error is "The installation failed, and the rollback has been performed." I suspect that permissions need to escalated and the user needs to approve this action for it to succeed. I have done some research and have tried to work around it but the user is never prompted. Does anyone know how to get this to work on Windows 7? I assume that Vista would have the same problem as well.
Other systems may have fewer, and there will likely be new versions in the future -- his install would need to detect which is available and will work.
I may have written an application with .net 2 that expects the .net 2 version -- but today someone may want to install it on a system with .net 4 only.
The .net 4 version will work, but the install won't know it's there and so will fail.
Of course, this is what the PATH environment variable is supposed to be used for, but I think I'm the only one who still uses it.
i wanted to know that is it possible to do interfacing with a biometric device like fingerprint recognition device with c#... I am planning of making a security system in which i will make a database (using sql) which will store and use data from the database using the input from fingerprint device and display from a gui using C# !!..
Sure, it's possible. You just need the SDK for the fingerprint scanner, oh, and a database to hold all the fingerprint data. You'll need to contect the manufacturer of the scanner to get the SDK and that is more than likely going to cost a few thousand dollars.
Never used it, but you have to buy a minimum of 5 licenses at $35 and change a piece for a total of $176. You also have to buy enough license to cover the number of machines you application is going to run on AND be developed on. So, if you're going to run this on 200 machines, you'll need the 150 pack ($3,920) + 50 singles ($1,765) + whatever dev machines you'll be using. $,$$$...