The .NET 3.0 is basically the same as .NET 2.0 except it also adds WPF, WCF, and Cardspace to the framework (I may be missing a category). .NET 3.0 is part of the foundation of Windows Vista and is not widely used on Windows XP or earlier computers so I would not use .NET 3.0 unless it is absolutely needed or if the target machine is running Windows Vista. In another year or so the .NET 3.0 may become the standard on all computers, but until then use it sparingly.
Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
I would say you cant set priority for the normal timer events:
all Windows.Forms.Timers get their event handled by the UI thread, hence at the same priority; it is unclear (I guess unspecified) in which order they would fire assuming
more than one of the timers is supposed to fire at a specific point in time
(maybe you will find my timers article interesting, it tells you more about the
resolution of the timer classes).
all other timers (Windows.Threading.Timer and Windows.Timers.Timer), as well as other
asynchronous events, typically use their own thread to service the event.
Here too, you typically dont control the thread's priority,
and the order of concurrent events is unspecified.
of course, you could organize a periodic event at a higher priority by using
your own thread, set at higher (maybe real-time) priority, and using a high-precision
timer (again see my article).
This is probably very simple but im having trouble getting my head around it.
Ive tried making a temporary list view item which stores the selected list view item,
Then move the selected list view item + 1 up one,
Then the selected list view item + 1 = the temporary,
But i keep getting errors.
Since this is not a question, I will only give a piece of advice:
- try to formulate a good, detailed and complete description of what you
want to achieve before you start implementing something
(e.g. what is swapping meant to do when three things are selected ?)
- then implement, test and debug it
- if stuck in a very specific thing, read the documentation, search Google or
codeproject, possibly launch a question here
- if stuck in general, publish all the above plus detailed description of the
behavior you observed and what it is you dont like about it.
I use below conection string, but there's appear error in remote connection.
On same pc connection is OK.
mConnection = new SqlConnection(@"data source=servername\sqlexpress;" +
Error mesage is:
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)
Server Authentication is SQL Server and Windows Authentication mode.
Allow remote connections to this server is set.
Your problem is that SQLExpress server by default has Named Pipes and TCP/IP protocol disabled. In order to connect to SQLExpress on different networked PC you should enable at least one of this protocols and restart your SQLExpress service under:
SQL Server Configuration Manager :: ... Network Configuration :: Protocols for ... :: Named Pipes and (or) TCP/IP.
Also it could be (but not necessary) required to setup client protocols on client PC.
Some other settings may be required on your firewalls and ...