Mmmh, ok danke schonmal für die Antwort. Aber wie/bzw welche parameter soll ich übergeben?

Moin.
Ich bin gerade dabei zu versuchen paar blöde daten in eine Access datenbank zu übergeben. Allerdings habe ich da noch paar probleme den Text zu bearbeiten.

Mein string wo mein prog. aufs maul fliegt sieht so aus:

"UPDATE tab_Preisliste SET PL_Bezeichnung = 'Halterung für 19'Serverschrank', PL_Preis = '90' WHERE PL_Baugruppe = '780071' AND PL_KPNummer = 999 AND PL_HGNummer = 999 AND PL_AGNummer = 999 AND PL_Version=3"

Der text "Bezeichnung" steht in einer Variable wo ich eigentlich mit Replace alle " ' " raus hole. Macht er in diesem Fall aber nicht. Meine Frage ist halt jetzt -> Wie bekomme ich am besten solche texte wo ich nicht immer weis was da für sonderzeichen sind in die Datenbank. Kann ich nicht irgendwie fertige DataRow's, DataTables oder DataSet's übertragen wo die Sonderzeichen dann drin bleiben können? Wenn das nicht geht. wie bekomm ich am besten " ' " das teil da rein?

MfG
Cook

Im Form die Eigenschaft KeyPreview auf true setzen.

So, ich bin jetzt kurz vorm verzweifeln.
Habe mir jetzt alle möglichen beiträge angeschaut zum Thema Textbox. Aber irgendwie nie gesehen das wirklich da einer ne Box nach seinen wünschen malen konnte ohne irgendwelche einschränkungen. Das kann doch net sein. Ich will nur den Border übermalen. Das kann ja wohl nicht so mega viel sein. Wenn ich mit SetVisualStyles arbeite und UserPaint auf true setze zeigt er mir den Text nicht mehr richtig an, und wenn ich es weg lasse funzt onPaint net. Kann mir da evtl. mal einer wirklich direkt helfen?? Mich würde schon interessieren ob es überhaupt mal einer gemacht hat 😜

MfG
Michael

Ok, hat sich erledigt.

Hey, will mir nen button machen, habe aber jetzt das problem dass das was ich selber male den text der in dem button steht übermalt. Also kann ich da kein text mehr anzeigen lassen.
Kennt einer das problem oder weis wie man das umgehen kann? Ich leite im moment von Button ab. Hatte erst label, aber da war das problem das ein label nicht auf die onGotFocus events anspringt.

Danke
Michael

Danke ... das mit dem Rectangle war genau das was ich gebrauct habe 😉

Euch beiden danke 😉

Kurze frage.
Wie kann ich irgendwo auf mein Control einen Pixel malen? Also nur einen. Mit drawLine wird es ja mindestens 2 pixel weit. Und ich wollt eiegentlich nicht erst ein Bitmap davon machen, dann den pixel malen und dann irgenwie wieder in mein Control bringen. Ist für ein Control

Vielen dank
Michael

Also es wird ja mein eigenes Control, also will ich mir da auch recht viel selber bauen. Deine antwort hat funktioniert. Das war schonmal gut. Nur hab ich jetzt gedacht ich brauch eine Hauptklasse für mein Control (´sozusagen TreeView) dann noch eine klasse für die Collection (sozusagen TreeNodeCollection) und noch eine für meine einzelnen Items ( TreeNode ). Hab ich das so richtig verstanden? Wenn ja muss ich mir nur noch anschauen wie ich meine Items in der Collection ablegen kann.

Nochmal danke.

MfG
Michael

Danke Herbivore, ich versuche was daraus zu machen. Aber noch ne fragen, von welchen klassen muss ich ableiten um so etwas hin zu bekommen wie bei einem treeView wenn man neue Nodes im Designer Hinzufügt? Da kann man das so schön machen mit Knoten, unterknoten und so.

MfG
Michael

Ich brauch mal wieder eure hilfe. Ich weis das es ein Thema ist was schon oft durchgekaut wurde, finde aber keine lösung.

Und zwar will ich ein Control bauen was dieser Windows Navigation entspricht. ( Diese Ausklapp-Menüs auf der linken seite z.B im Arbeitsplatz) Jetzt habe ich mir überlegt ich mache es aus 3 Teilen. Dem Hauptcontrol wo alles drauf kommt, dann eine Collection der Gruppen und noch eine Collection mit den dazu gehörigen Items in den Gruppen? Wie würdet ihr das realisieren?? Ich bin irgendwie auf dem Falschen Weg.
Mein Hauptcontrol leite ich momentan von IList ab weil es ja die einzelnen Gruppen sammeln muss. Die Einzelnen gruppen leite ich auch von IList ab und die items von Label.

Kann man daraus irgendwas machen oder muss ich ganz von vorne anfangen?

MfG
Michael

Mmmh, dann werde ich wohl die mdb nehmen.

Danke 🙂

Nochmal ne Frage,
ich habe ein Datagrid mit 4 spalten, den inhalt von diesem grid möchte ich gerne speichern damit ich beim nächsten programmstart wieder damit arbeiten kann. Sollte ich das mit eine *.mdb datei machen, xml oder sonst was? Wie würdet ihr es machen?

Danke
cook

Ah danke, hät ich auch drauf kommen können 😉 .
War wohl doch etwas zu spät.

MfG
cook

Morgen,
hab da mal ne frage wie ich ein node aus einer xml datei lösche.
Die hat folgendes schema:

<?xml version="1.0" encoding="utf-8"?>
<test>
  <GROUP>
    <title>NEWS</title>
    <item>
      <title>
        name
      </title>
      <link>
        test
      </link>
    </item>
    <item>
      <title>
        test2
      </title>
      <link>
        test2
      </link>
    </item>
  </GROUP>
  <GROUP>
    <title>test3</title>
    <item>
      <title>test3</title>
      <link>test3</link>
    </item>
  </GROUP>
</test>

Aus dem ding möchte ich jetzt so ein kompletten "GROUP" node löschen. Aber ich kann immer nur removeAll nodes... das problem ist dann das ich ja dann von test remove all machen müsste und dann wär ja alles weg =). Einer ne idee?

Naja, da kann man dann wohl nix machen.
Werde mich dann auf andere RSS seiten beschränken (gibt ja genug).

Vielen dank herbi 🙂

Leider auch nicht 🙁
Aber ich hab jetzt auch mal getestet mit so geläufigen Rss-Readern und die konnten alle nicht die seiten von Microsoft lesen ... 8o

mmmh... damit funzt es auch : http://www.chip.de/rss_news.xml

Ja, wenn ich die datei erst runterlade funktioniert es. Aber das find ich eher nicht so cool 😉... kann es daran liegen das es kein "direkter" link auf die xml datei ist? also nicht sowas wie www.microsoft.de/test.xml.

Hey,
ich versuche grade so einen kleinen RSS-Reader zu schreiben. Jetzt würde ich gerne RSS files direkt "öffnen"
versucht habe ich es mit

 
XmlDocument xDoc = new XmlDocument();

xDoc.Load("http://www.microsoft.com/germany/events/rss/default.aspx?IsPostBack&EventCategory=Webcast-Live&TargetAudience=B%FCroanwender");

Ist jetzt mal ein bsp. link. Er wirft mir aber dann eine exception.:

Der Remoteserver hat einen Fehler zurückgegeben: (500) Interner Serverfehler.

Kan mir da einer helfen? Muss ich die RSS files erst runterladen um damit arbeiten zu können?

MfG
Cook

Morgen,
könnte mir mal einer von euch sagen wie ich einstellen kann wo mein Programm nach meinen Dlls suchen soll? Also ich hätte gerne einen extra Ordner in meinem programm-ordner, wo alle meine Dlls drin sind.

greetz
cook

Werd ich mal machen. Hab mich halt im Hinterkopf die ganze zeit sehr stark an Miranda-IM gestützt.. (Messanger) ... dort ist das mit den plugin sehr einfach gehalten und es kommen im hauptprogramm neue Items in Context-Menüs und so weiter ... muss ich wohl mal etwas lesen.

Aber so wie ich das jetzt hier in den beispielen sehe, steht in der Interface.dll immer schon der Methodenname den es in einer DLL gibt. Was also wenn ich eine neue dll bei füge und die Methoden da einen anderen namen haben? Oder soll man immer sozusagen eine einstiegsmethode benutzen auf die die interface.dll zugreift? Ist irgendwie im moment etwas schwer zu verstehen für mich 🙁 .

Ist zwar schon etwas her aber ich beschäftige mich auch grad mit dem Thema (Auch schon ein Thread offen), aber hier ist eigentlich genau wie ich das suche und im moment auch verstehe. Naja, nicht so ganz. Und zwar hab ich die logik noch nicht verstanden. Angenommen ich hab jetzt mein Programm. Da sollen dann mal plugins rein. Ein Plugin wäre dann nur eine DLL datei die ich in einen ordner mache. (Plugins). Jetzt soll mein Prog beim starten alle Dlls auslesen und wenn möglich einbinden. nur das mit der interface.dll versteh ich nicht. Heist das ich müsste mit jeder neuen DLL eine Interface.dll mit geben wo die methoden drin sind?

Hab doch noch ne frage. Wenn ich jetzt einen ordner auslese wo die plugins drin sind, wie kann ich die Dlls jetzt einbinden? Also ich weis ja dann beim start nur wo die Dlls sind + den name.

Kann man darauf irgendwie events oder sowas machen? Oder wie mache ich es am besten das ich immer wenn sich der Wert ein Variable ändert eine Methode starte?

Danke Herbivore.
Hast mir mit den Antworten eigentlich alles gesagt was ich wissen wollte/muss.
Bin mir halt oft nicht so sicher ob die art wie ich denke etwas machen zu wollen die richtige ist. Man will sich ja nichts falsches anlernen 😉.

Steam ist so ein Updater für Counter-strike Source und andere programme. Ist aber egal 😉

Das mit dem updater guck ich mir auch mal an @ talla .. danke

Ok, das mit den plugins suche ich dann nochmal. Bei dem link von dir ist ja eigentlich nur das bekommen von der neuen version besprochen. Das dürfte ja kein problem sein denke ich. Mein problem ist. Wie aktualisiere ich mein programm? Tauscht man dann einfach die ganzen Exe/Dll files aus? ... kann man irgendwie eine bestehende datei ergenzen oder so? Wie wird das bei großen sachen wie zB. Steam gemacht?

Thx herbivore 🙂

Morgen,
ich habe vor demnächst mal ein kleines projekt in angriff zu nehmen. Dabei würde ich mir gerne die möglich keit offen lassen später updates machen zu können und plugins die ich geschrieben habe einzubinden. Nur weis ich da überhaupt nicht wie ich anfangen soll, bzw auch nicht nach was ich suchen soll. Das mit den updates sollte später mal so laufen das ich mit meinem programm prüfe ob es neue updates gibt, und wenn ja sollen die gezogen werden. Plugins habe ich mir gedacht wie bei Miranda, weis nicht ob ihr es kennt, aber auf jedenfall legt man da einfach nur pro plugin eine DLL ins plugin verzeichniss und es ist drin. Ein neu start und er benutzt das teil.

MfG
cook

Musst dabei nur etwas aufpassen. Wenn du unten dann e.HasMorePages auf true gesetzt hast kannste dir dein ganzes PrintDoc vorstellen wie eine schleife. Also alle counter und so weiter die du in deinem printDoc oben setzt werden überschrieben. Achso, und du solltest dir sicher sein irgendwann wieder auf false gesetzt zu haben weil sonst kommten da paar seiten raus 😁

Hast du schon versucht einfach die Microsoft.Office.Interop.dll einzubinden und damit mit excel daten auszutauschen? Bedarf einer gewissen zeit einarbeitung aber dann könntest du das ganze manuell mit einer schleife in Excel rein schreiben... so mache ich es immer.

Hast du einen verweis auf die stelle wo das steht??

Ich weis das es auch anders geht .. aber ich will halt jetzt wissen wo hier der fehler ist.
Ne ich kopier die nicht aufeinander ... hab nur hier andere namen gegeben. Ist eigentlich ne andere datei.

Hey,
hab mich heute, weil ich nicht weis was ich machen soll etwas mit APIs befasst. Jetzt habe ich versuch damit eine datei zu kopieren. Arbeite mit FileCopyEx aus der Kernel32.dll... habe also einen button gemacht bei dem auf click die datei kopiert werden soll. Allerdings passiert erst nicht. Wenn ich dann nochmal auf den button drücke schmeist der mir ne Exception und die datei ist plötzlich kopiert.... kann mir da einer helfen?

CopyFileEx(@"C:\test.exe", @"C:\test.exe", null, null, false, "COPY_FILE_FAIL_IF_EXISTS");

guck dir das mal an:
System.Environment.TickCount

😉

Also ich hab das jetzt auch mal versucht. Kann mir mal einer sagen warum das Event bei mir nicht anspringt? Der reagiert garnicht darauf... Hab auch onPain versucht. Funktioniert auch net.

Also mit dem Contextmenü komm ich kein stück weiter. In wie weit kann ich damit eigentlich das design verändern?

Ja stimmt. Sorry. Ich arbeite mit 1.1 ... wir stellen erst im Februar auf 2.0 um 😉

Na wenn ich das mal hin bekomme ... Du sagst das so einfach 😜 ... muss erst mal ein anfang finden.

EDIT: Dumme frage, aber kann es sein das ein Contextmenü kein OnPaint hat?

Weil ich mich noch nicht mit ableiten befasst habe 😁 ... werd ich dann wohl mal langsam tun müssen. 🙁

Es ging mir eigentlich bei der sache hauptsächlich um das design der box zu ändern ... ist das mit vererbung möglich? ... weis ja nicht wie weit man dass dann alles bearbeiten kann.

Hey,
also ich will mir ein eigenes Context menü bauen. Mein Grundgedanke war eigentlich ein form ohne border und da halt einzelne labels drin. Hab aber jetzt das Problem, dass wenn man den ersten rechtsklick gemacht hat das form ja erscheint. Da ich aber sozusagen jedes mal beim rechtsklick ein neues objekt mache bekomm ich das alte Form nicht zu. Wie könnte ich jetzt mit einem rechtsklick das Form Schliessen? Am ende soll es so sein das ich alles in eine DLL packe und dann einfach in meine programme einbinden kann.

Thx Michael

Das stand in der txt die beim download von Codeproject dabei ist:

GNU LESSER GENERAL PUBLIC LICENSE  
         Version 2.1, February 1999  

Copyright (C) 1991, 1999 Free Software Foundation, Inc.
59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.

[This is the first released version of the Lesser GPL. It also counts
as the successor of the GNU Library Public License, version 2, hence
the version number 2.1.]

  	    Preamble  

The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public
Licenses are intended to guarantee your freedom to share and change
free software--to make sure the software is free for all its users.

This license, the Lesser General Public License, applies to some
specially designated software packages--typically libraries--of the
Free Software Foundation and other authors who decide to use it. You
can use it too, but we suggest you first think carefully about whether
this license or the ordinary General Public License is the better
strategy to use in any particular case, based on the explanations below.

When we speak of free software, we are referring to freedom of use,
not price. Our General Public Licenses are designed to make sure that
you have the freedom to distribute copies of free software (and charge
for this service if you wish); that you receive source code or can get
it if you want it; that you can change the software and use pieces of
it in new free programs; and that you are informed that you can do
these things.

To protect your rights, we need to make restrictions that forbid
distributors to deny you these rights or to ask you to surrender these
rights. These restrictions translate to certain responsibilities for
you if you distribute copies of the library or if you modify it.

For example, if you distribute copies of the library, whether gratis
or for a fee, you must give the recipients all the rights that we gave
you. You must make sure that they, too, receive or can get the source
code. If you link other code with the library, you must provide
complete object files to the recipients, so that they can relink them
with the library after making changes to the library and recompiling
it. And you must show them these terms so they know their rights.

We protect your rights with a two-step method: (1) we copyright the
library, and (2) we offer you this license, which gives you legal
permission to copy, distribute and/or modify the library.

To protect each distributor, we want to make it very clear that
there is no warranty for the free library. Also, if the library is
modified by someone else and passed on, the recipients should know
that what they have is not the original version, so that the original
author's reputation will not be affected by problems that might be
introduced by others.

Finally, software patents pose a constant threat to the existence of
any free program. We wish to make sure that a company cannot
effectively restrict the users of a free program by obtaining a
restrictive license from a patent holder. Therefore, we insist that
any patent license obtained for a version of the library must be
consistent with the full freedom of use specified in this license.

Most GNU software, including some libraries, is covered by the
ordinary GNU General Public License. This license, the GNU Lesser
General Public License, applies to certain designated libraries, and
is quite different from the ordinary General Public License. We use
this license for certain libraries in order to permit linking those
libraries into non-free programs.

When a program is linked with a library, whether statically or using
a shared library, the combination of the two is legally speaking a
combined work, a derivative of the original library. The ordinary
General Public License therefore permits such linking only if the
entire combination fits its criteria of freedom. The Lesser General
Public License permits more lax criteria for linking other code with
the library.

We call this license the "Lesser" General Public License because it
does Less to protect the user's freedom than the ordinary General
Public License. It also provides other free software developers Less
of an advantage over competing non-free programs. These disadvantages
are the reason we use the ordinary General Public License for many
libraries. However, the Lesser license provides advantages in certain
special circumstances.

For example, on rare occasions, there may be a special need to
encourage the widest possible use of a certain library, so that it becomes
a de-facto standard. To achieve this, non-free programs must be
allowed to use the library. A more frequent case is that a free
library does the same job as widely used non-free libraries. In this
case, there is little to gain by limiting the free library to free
software only, so we use the Lesser General Public License.

In other cases, permission to use a particular library in non-free
programs enables a greater number of people to use a large body of
free software. For example, permission to use the GNU C Library in
non-free programs enables many more people to use the whole GNU
operating system, as well as its variant, the GNU/Linux operating
system.

Although the Lesser General Public License is Less protective of the
users' freedom, it does ensure that the user of a program that is
linked with the Library has the freedom and the wherewithal to run
that program using a modified version of the Library.

The precise terms and conditions for copying, distribution and
modification follow. Pay close attention to the difference between a
"work based on the library" and a "work that uses the library". The
former contains code derived from the library, whereas the latter must
be combined with the library in order to run.

    GNU LESSER GENERAL PUBLIC LICENSE  

TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

0. This License Agreement applies to any software library or other
   program which contains a notice placed by the copyright holder or
   other authorized party saying it may be distributed under the terms of
   this Lesser General Public License (also called "this License").
   Each licensee is addressed as "you".

A "library" means a collection of software functions and/or data
prepared so as to be conveniently linked with application programs
(which use some of those functions and data) to form executables.

The "Library", below, refers to any such software library or work
which has been distributed under these terms. A "work based on the
Library" means either the Library or any derivative work under
copyright law: that is to say, a work containing the Library or a
portion of it, either verbatim or with modifications and/or translated
straightforwardly into another language. (Hereinafter, translation is
included without limitation in the term "modification".)

"Source code" for a work means the preferred form of the work for
making modifications to it. For a library, complete source code means
all the source code for all modules it contains, plus any associated
interface definition files, plus the scripts used to control compilation
and installation of the library.

Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope. The act of
running a program using the Library is not restricted, and output from
such a program is covered only if its contents constitute a work based
on the Library (independent of the use of the Library in a tool for
writing it). Whether that is true depends on what the Library does
and what the program that uses the Library does.

1. You may copy and distribute verbatim copies of the Library's
   complete source code as you receive it, in any medium, provided that
   you conspicuously and appropriately publish on each copy an
   appropriate copyright notice and disclaimer of warranty; keep intact
   all the notices that refer to this License and to the absence of any
   warranty; and distribute a copy of this License along with the
   Library.

You may charge a fee for the physical act of transferring a copy,
and you may at your option offer warranty protection in exchange for a
fee.

2. You may modify your copy or copies of the Library or any portion
   of it, thus forming a work based on the Library, and copy and
   distribute such modifications or work under the terms of Section 1
   above, provided that you also meet all of these conditions:

a) The modified work must itself be a software library.  

b) You must cause the files modified to carry prominent notices  
stating that you changed the files and the date of any change.  

c) You must cause the whole of the work to be licensed at no  
charge to all third parties under the terms of this License.  

d) If a facility in the modified Library refers to a function or a  
table of data to be supplied by an application program that uses  
the facility, other than as an argument passed when the facility  
is invoked, then you must make a good faith effort to ensure that,  
in the event an application does not supply such function or  
table, the facility still operates, and performs whatever part of  
its purpose remains meaningful.  

(For example, a function in a library to compute square roots has  
a purpose that is entirely well-defined independent of the  
application.  Therefore, Subsection 2d requires that any  
application-supplied function or table used by this function must  
be optional: if the application does not supply it, the square  
root function must still compute square roots.)  

These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Library,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based
on the Library, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote
it.

Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Library.

In addition, mere aggregation of another work not based on the Library
with the Library (or with a work based on the Library) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.

3. You may opt to apply the terms of the ordinary GNU General Public
   License instead of this License to a given copy of the Library. To do
   this, you must alter all the notices that refer to this License, so
   that they refer to the ordinary GNU General Public License, version 2,
   instead of to this License. (If a newer version than version 2 of the
   ordinary GNU General Public License has appeared, then you can specify
   that version instead if you wish.) Do not make any other change in
   these notices.

Once this change is made in a given copy, it is irreversible for
that copy, so the ordinary GNU General Public License applies to all
subsequent copies and derivative works made from that copy.

This option is useful when you wish to copy part of the code of
the Library into a program that is not a library.

4. You may copy and distribute the Library (or a portion or
   derivative of it, under Section 2) in object code or executable form
   under the terms of Sections 1 and 2 above provided that you accompany
   it with the complete corresponding machine-readable source code, which
   must be distributed under the terms of Sections 1 and 2 above on a
   medium customarily used for software interchange.

If distribution of object code is made by offering access to copy
from a designated place, then offering equivalent access to copy the
source code from the same place satisfies the requirement to
distribute the source code, even though third parties are not
compelled to copy the source along with the object code.

5. A program that contains no derivative of any portion of the
   Library, but is designed to work with the Library by being compiled or
   linked with it, is called a "work that uses the Library". Such a
   work, in isolation, is not a derivative work of the Library, and
   therefore falls outside the scope of this License.

However, linking a "work that uses the Library" with the Library
creates an executable that is a derivative of the Library (because it
contains portions of the Library), rather than a "work that uses the
library". The executable is therefore covered by this License.
Section 6 states terms for distribution of such executables.

When a "work that uses the Library" uses material from a header file
that is part of the Library, the object code for the work may be a
derivative work of the Library even though the source code is not.
Whether this is true is especially significant if the work can be
linked without the Library, or if the work is itself a library. The
threshold for this to be true is not precisely defined by law.

If such an object file uses only numerical parameters, data
structure layouts and accessors, and small macros and small inline
functions (ten lines or less in length), then the use of the object
file is unrestricted, regardless of whether it is legally a derivative
work. (Executables containing this object code plus portions of the
Library will still fall under Section 6.)

Otherwise, if the work is a derivative of the Library, you may
distribute the object code for the work under the terms of Section 6.
Any executables containing that work also fall under Section 6,
whether or not they are linked directly with the Library itself.

6. As an exception to the Sections above, you may also combine or
   link a "work that uses the Library" with the Library to produce a
   work containing portions of the Library, and distribute that work
   under terms of your choice, provided that the terms permit
   modification of the work for the customer's own use and reverse
   engineering for debugging such modifications.

You must give prominent notice with each copy of the work that the
Library is used in it and that the Library and its use are covered by
this License. You must supply a copy of this License. If the work
during execution displays copyright notices, you must include the
copyright notice for the Library among them, as well as a reference
directing the user to the copy of this License. Also, you must do one
of these things:

a) Accompany the work with the complete corresponding  
machine-readable source code for the Library including whatever  
changes were used in the work (which must be distributed under  
Sections 1 and 2 above); and, if the work is an executable linked  
with the Library, with the complete machine-readable "work that  
uses the Library", as object code and/or source code, so that the  
user can modify the Library and then relink to produce a modified  
executable containing the modified Library.  (It is understood  
that the user who changes the contents of definitions files in the  
Library will not necessarily be able to recompile the application  
to use the modified definitions.)  

b) Use a suitable shared library mechanism for linking with the  
Library.  A suitable mechanism is one that (1) uses at run time a  
copy of the library already present on the user's computer system,  
rather than copying library functions into the executable, and (2)  
will operate properly with a modified version of the library, if  
the user installs one, as long as the modified version is  
interface-compatible with the version that the work was made with.  

c) Accompany the work with a written offer, valid for at  
least three years, to give the same user the materials  
specified in Subsection 6a, above, for a charge no more  
than the cost of performing this distribution.  

d) If distribution of the work is made by offering access to copy  
from a designated place, offer equivalent access to copy the above  
specified materials from the same place.  

e) Verify that the user has already received a copy of these  
materials or that you have already sent this user a copy.  

For an executable, the required form of the "work that uses the
Library" must include any data and utility programs needed for
reproducing the executable from it. However, as a special exception,
the materials to be distributed need not include anything that is
normally distributed (in either source or binary form) with the major
components (compiler, kernel, and so on) of the operating system on
which the executable runs, unless that component itself accompanies
the executable.

It may happen that this requirement contradicts the license
restrictions of other proprietary libraries that do not normally
accompany the operating system. Such a contradiction means you cannot
use both them and the Library together in an executable that you
distribute.

7. You may place library facilities that are a work based on the
   Library side-by-side in a single library together with other library
   facilities not covered by this License, and distribute such a combined
   library, provided that the separate distribution of the work based on
   the Library and of the other library facilities is otherwise
   permitted, and provided that you do these two things:

a) Accompany the combined library with a copy of the same work  
based on the Library, uncombined with any other library  
facilities.  This must be distributed under the terms of the  
Sections above.  

b) Give prominent notice with the combined library of the fact  
that part of it is a work based on the Library, and explaining  
where to find the accompanying uncombined form of the same work.  

8. You may not copy, modify, sublicense, link with, or distribute
   the Library except as expressly provided under this License. Any
   attempt otherwise to copy, modify, sublicense, link with, or
   distribute the Library is void, and will automatically terminate your
   rights under this License. However, parties who have received copies,
   or rights, from you under this License will not have their licenses
   terminated so long as such parties remain in full compliance.

9. You are not required to accept this License, since you have not
   signed it. However, nothing else grants you permission to modify or
   distribute the Library or its derivative works. These actions are
   prohibited by law if you do not accept this License. Therefore, by
   modifying or distributing the Library (or any work based on the
   Library), you indicate your acceptance of this License to do so, and
   all its terms and conditions for copying, distributing or modifying
   the Library or works based on it.

10. Each time you redistribute the Library (or any work based on the
    Library), the recipient automatically receives a license from the
    original licensor to copy, distribute, link with or modify the Library
    subject to these terms and conditions. You may not impose any further
    restrictions on the recipients' exercise of the rights granted herein.
    You are not responsible for enforcing compliance by third parties with
    this License.

11. If, as a consequence of a court judgment or allegation of patent
    infringement or for any other reason (not limited to patent issues),
    conditions are imposed on you (whether by court order, agreement or
    otherwise) that contradict the conditions of this License, they do not
    excuse you from the conditions of this License. If you cannot
    distribute so as to satisfy simultaneously your obligations under this
    License and any other pertinent obligations, then as a consequence you
    may not distribute the Library at all. For example, if a patent
    license would not permit royalty-free redistribution of the Library by
    all those who receive copies directly or indirectly through you, then
    the only way you could satisfy both it and this License would be to
    refrain entirely from distribution of the Library.

If any portion of this section is held invalid or unenforceable under any
particular circumstance, the balance of the section is intended to apply,
and the section as a whole is intended to apply in other circumstances.

It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system which is
implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.

This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.

12. If the distribution and/or use of the Library is restricted in
    certain countries either by patents or by copyrighted interfaces, the
    original copyright holder who places the Library under this License may add
    an explicit geographical distribution limitation excluding those countries,
    so that distribution is permitted only in or among countries not thus
    excluded. In such case, this License incorporates the limitation as if
    written in the body of this License.

13. The Free Software Foundation may publish revised and/or new
    versions of the Lesser General Public License from time to time.
    Such new versions will be similar in spirit to the present version,
    but may differ in detail to address new problems or concerns.

Each version is given a distinguishing version number. If the Library
specifies a version number of this License which applies to it and
"any later version", you have the option of following the terms and
conditions either of that version or of any later version published by
the Free Software Foundation. If the Library does not specify a
license version number, you may choose any version ever published by
the Free Software Foundation.

14. If you wish to incorporate parts of the Library into other free
    programs whose distribution conditions are incompatible with these,
    write to the author to ask for permission. For software which is
    copyrighted by the Free Software Foundation, write to the Free
    Software Foundation; we sometimes make exceptions for this. Our
    decision will be guided by the two goals of preserving the free status
    of all derivatives of our free software and of promoting the sharing
    and reuse of software generally.

        NO WARRANTY  
    

15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
    WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
    EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
    OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY
    KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
    IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
    PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
    LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
    THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
    WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
    AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU
    FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
    CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
    LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
    RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
    FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
    SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
    DAMAGES.

     END OF TERMS AND CONDITIONS  
    
     How to Apply These Terms to Your New Libraries  
    

If you develop a new library, and you want it to be of the greatest
possible use to the public, we recommend making it free software that
everyone can redistribute and change. You can do so by permitting
redistribution under these terms (or, alternatively, under the terms of the
ordinary General Public License).

To apply these terms, attach the following notices to the library. It is
safest to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least the
"copyright" line and a pointer to where the full notice is found.

<one line to give the library's name and a brief idea of what it does.>  
Copyright (C) <year>  <name of author>  

This library is free software; you can redistribute it and/or  
modify it under the terms of the GNU Lesser General Public  
License as published by the Free Software Foundation; either  
version 2.1 of the License, or (at your option) any later version.  

This library is distributed in the hope that it will be useful,  
but WITHOUT ANY WARRANTY; without even the implied warranty of  
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU  
Lesser General Public License for more details.  

You should have received a copy of the GNU Lesser General Public  
License along with this library; if not, write to the Free Software  
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA  

Also add information on how to contact you by electronic and paper mail.

You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the library, if
necessary. Here is a sample; alter the names:

Yoyodyne, Inc., hereby disclaims all copyright interest in the
library `Frob' (a library for tweaking knobs) written by James Random Hacker.

<signature of Ty Coon>, 1 April 1990
Ty Coon, President of Vice

That's all there is to it!

Kann man irgendwie auslesen was für eine art Drive z.B. C ist? Also ich habe mit System.Environment.GetLogicalDrives() alle laufwerke ausgelesen. Jetzt müsste ich aber rausbekommen was für ein typ laufwerk das ist.

Kann man das im nachhinein noch oder muss ich mit WMI arbeiten?

c1FlexGridClassic1.Cell[C1.Win.C1FlexGrid.Classic.CellPropertySettings.flexcpBackColor, 1, 2] = Color.LightGray;

Hey, also so wie ich das sehe hast du doch bestimmt das komplette paket von C1? Wenn ja bentze doch einfach das C1FlexGridClassic..... ist viel besser. Und auf deine frage dann -> wenn du die Hintergrundfarbe meinst:

C1FlexGridClassic.CellBackColor

File.Copy()

Hätte auch mal ne kurze frage zu dem Thema.... wollte mir auch so ein TreeView machen. Dann wollte ich sowas machen mit foreach(TreeNode ... bla das der mir halt für jeden node den das teil hat etwas macht. Am besten sogar nur für die nodes die in dem expandierten sind.

Tipp?

thx cook

Danke leutz ... funzt jetzt

Eure exceptions 😉

@Cadi:
Leeres Zeichenliteral

@DeveloperX
Zeichenfolge kann keine Nullänge haben.

Jo das mit der bestimmten anzahl war mir klar... stimmt eigentlich. Muss ja immer 30 zeichen sein bei titel und interpret 😉
thx

EDIT: Funzt auch nicht ... zeichen sind immernoch drin.