|
SledgeHammer01 wrote: How do you figure?
Easy: epic fail on my part.
However, I do agree with Dave K's suggestion that you build your parameters into a variable so you can see exactly what is being sent to the command processor.
Use the best guess
|
|
|
|
|
There is no overload of Process.Start that allows the executable filename and arguments to be combined into one string. I suspect that you'll find that the documentation[^] will be a great help in your endeavours.
[EDIT] Sorry ignore this, I've just looked at your code again and see that I can't read!
Alan.
|
|
|
|
|
It does? How do you figure?
System.Diagnostics.Process.Start("sc", "\\\\" + strMachine + " config \"<the service="" name="">\" start= demand");
The first param is "sc" and then there's a comma there and the second param is the argument string.
|
|
|
|
|
Sorry for the late response. I think there an old carpenter's adage which goes something like "measure twice and cut once". As I hadn't spotted that comma I guess I should have read twice and then not answered at all!
Alan.
|
|
|
|
|
The applications I write typically involve a lot of data entry, for use in a warehouse/manufacturing environment. Sometimes there can be many different fields, sometimes not so much. But I've always found it a bit tedious and time consuming to restore the UI to its initial state when the user saves an entry, for example.
I mean, a form could have buttons that are disabled initially, a few entry fields that are disabled at first waiting for other input, several input fields that need to be cleared, etc. What is the best method to go about resetting a form once the user is done? I've always just used "thisField.Enabled = false;" and "thatField.Text = string.Empty;" and so on. But is there a more efficient method for achieving this?
djj55: Nice but may have a permission problem
Pete O'Hanlon: He has my permission to run it.
|
|
|
|
|
Replacing the form with a new instance would be a shortcut to "restore" the initial state.
|
|
|
|
|
I could have clarified "form", since I'm referring to WinForms applications. "Form" in this context was actually meant as an input form, not the window itself. But I think I can follow that same concept. I'll give it a try.
djj55: Nice but may have a permission problem
Pete O'Hanlon: He has my permission to run it.
|
|
|
|
|
Oh duh... OK...
You can reset a form...
myForm.Controls.Clear();
myForm.InitializeComponent();
|
|
|
|
|
Thank you, I'll give this a try. Very simple and seems like it should do exactly what I need. 
djj55: Nice but may have a permission problem
Pete O'Hanlon: He has my permission to run it.
|
|
|
|
|
The only problem with doing that is that if your form code maintains a state it's not going to get reset. It'll only destroy and recreate the controls to however you had them set in the Form Designer and property settings.
|
|
|
|
|
But isn't that what he wants? Instead of "clearing" everything, which sets textboxes to empty string and whatnot, I thought he wants the "default" values from the form designer to show up - otherwise, yeah, you only need to Form.Controls.Clear() and call it good.
|
|
|
|
|
I don't let the controls determine the status of any state machine I've got behind the forms. The state machine determines the state of the controls and the controls reflect that.
I know there are plenty of cases where the app or form is so simple that there is no state machine behind it, but there are too many noobs out there who rely on the controls to "store" data and determine the state of a form or app based on, say, the text of a button, or if it's enabled or not.
That's not the proper way to do it.
|
|
|
|
|
Yeah definitely incorrect designs would make it more tricky, but I get the impression this particular form doesn't have any initial state other than what was set in the designer...
|
|
|
|
|
While it's a good idea  , I'd still call it a hack, unless xml-documentation is included with some explanation like Dave posted. Private members would not be reset, and the "OnCreate" event wouldn't fire on it's own. It might contain some "form magic" for setting the form up as well.
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
|
|
|
|
|
Well, I used the "hack" and it works just fine. I'm still going to experiment with other options based on everyone's input. But for my purposes, the "hack" gets the job done for now at least. 
djj55: Nice but may have a permission problem
Pete O'Hanlon: He has my permission to run it.
|
|
|
|
|
I just re-load the page...
If you're currently on "MyPage.aspx" this will reset it.
Response.Redirect("MyPage.aspx", true);
|
|
|
|
|
Matt U. wrote: But I've always found it a bit tedious and time consuming to restore the UI to its initial state when the user saves an entry, for example.
Form.Controls.Clear();
InitializeComponent();
Alternatively, loop all controls using reflection (no, it ain't that slow, just a bit of an exercise to get recursion working) and clear them.
How do your edit-forms look like? Mine could be explained as a PropertyGrid on a dialog-form. It has an extra button called "reset", which just reloads a cloned object into the propertygrid.
It's not a real property-grid anymore; it's a custom control that behaves in a similar way (in code), but that renders a more 'traditional' winform.
I choose this architecture out of convenience; a single modification in the object, and it's pushed to a Memento-pattern (undo/redo stack). When closing, the content of both get serialized and saved. When loaded, both are restored - it makes users happy when they find out that they can "undo" yesterday's changes, even if the PC was turned of in the mean time.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
Eddy Vluggen wrote: they can "undo" yesterday's changes
THAT, is hard freeking core, dude. I like it
As noted before though, I think the only way to make it behave like a 'new' form is to have it be a new form... but if it's your main form or something, that might require hacking program.cs.
|
|
|
|
|
Jasmine2501 wrote: I like it
Tx
Can be a bit confusing though; most users expect an empty undo/redo-list when they launch an application.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
If you are using wpf with MVVM then all you have to do is make the VM serializable, and save it.
|
|
|
|
|
hi my friends
i 'll create an Attendance System in c sharp and a table in sql
but i do not know this table form.
plz help this segment
tnx
|
|
|
|
|
This is not a good question - we cannot work out from that little what you are trying to do.
Remember that we can't see your screen, access your HDD, or read your mind.
Try giving an example of what is giving you a problem.
The universe is composed of electrons, neutrons, protons and......morons. (ThePhantomUpvoter)
|
|
|
|
|
behrouz shamlo wrote: i 'll create an Attendance System in c sharp and a table in sql
but i do not know this table form.
Is requested regularly, and there are quite some examples on the web. Simply download the Time Tracker Starter Kit[^].
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
This is more of a SQL considering you are looking for the structure of the table.
Try looking at samples across the internet to identify your fields correctly.
|
|
|
|
|
Abhinav S wrote: Try looking at samples across the internet to identify your fields correctly.
I really dislike this MO; "go find a decent db on the netz".
Make a list of all the facts that your information-system needs to administer. Group the facts into logical groupings. Make sure every fact is atomic; if it's not, split it into multiple facts.
Iterate each group, giving it a descriptive name for the fact-collection. Now, iterate again, and find the fact (or facts) in each group that uniquely identifies a row/record/tupel/object whatever you call it. That's the fact(s) (or field(s) or column(s)) that represent the primary key.
Next, iterate all those tables/groups of facts again, and remove any fact that's not being identified by it's key.
This is called "database-design and normalization", and is a bit more work than described above.
And no, a housenumber "21a" does NOT consist of two facts, that's ONE fact. (Person has one housenumber, which happens to be a combination of two real-life things. These are, however, never used irl as separate facts, and hence, should not be modelled as different facts. Same goes for street and housenumber; if you need an address, reserve space for an address, not a street and a housenumber.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
