I apologise in advance if there is any vagueness, but I am struggling with even knowing where to start with this one.
We have an app written in C# & .Net framework 4.6.2. installed at numerous customers working with out issue. At one customer all the 'OK' button controls need to be clicked twice rather than once to work. There are numerous different programs that don't have any common code, but still exhibit the same behaviour.
I am suspecting a windows issue rather than app, but done't know where to start. Could anyone point me in the right direction please?
cheers
Rich
Related
I'm having a hard time finding any documentation on how to interact with the SCSM Console.
Almost all samples and documentation I stumble upon, are regarding interacting with the System Center Backend.
My goal is to have a TextBox and a Button, in the TextBox goes an Incident ID, and a click on the button would then open the incident in the SCSM Console.
I don't know if its even possible, does anyone of you have experience with this?
I've worked with the SCSM SDK for 2 years now and have not come across anything within it which would allow you to launch the console and go straight to a particular incident form. The ConsoleContextHelper requires the console to be already open and mainly interacts with the current view/form.
lovedatsnow's suggestion for using a ConsoleTask on the incident view would be the closest way to implement something similar to what you desire however this wouldn't give much advantage over using the search bar and double clicking the result to open the form.
I've walked through Travis Wright's post with success:
https://blogs.technet.microsoft.com/servicemanager/2010/02/11/tasks-part-1-tasks-overview/
Here is a simpler tutorial that may also be helpful
https://blog.jhnr.ch/2013/12/09/how-to-create-a-custom-scsm-console-task-by-using-some-c-and-xml-magic/
I'm working on a Windows CE project and have run into a strange problem. When i display a messagebox the physical key stop working. The project relies solely on key input which work fine when changing focus between objects on the form. Because i can't slect an option from the message box, the application basically locks out.
I initially thought my keydown handler was to blame but i discovered the same issue regardless of the keydown handler (even in a new project it doesn't work)
I've been looking around online for information but the only thing i've come across involves changing messagebox buttons. The most prominent solution is to create your own messageboxes but it seems like a waste for what i need. Is there a more efficient way of solving this problem?
I'm creating a C# program and I need to control another application. I found this
example, but it doesn't really work for me (or at least I can't make it work).
1) The application is already running (so I can't use Application application = Application.Launch("foo.exe");
2) It has a textbox and I need to read what's written in it.
3) Then I want to press one of its buttons (This can be done with that: Button button = window.Get<Button>("save"); button.Click();
I also searched Google, but I didn't find anything working.
Can you help me? Thanks in advance.
The documentation doesn't mention it, but Application.Attach() allows you to access a program that is already running. From there, I would expect everything would work as documented.
When I run my application, do some work on it and click the language button on the Windows taskbar and change the input language, my C# application freezes displaying an hourglass cursor. Does anyone have any idea on what may be going wrong? I have absolutely no clue where to start...
First of all, your problem is hard to follow, since we don't know what is going on in your application. Neither we know which exactly code in your application freezes.
For others, the problem in your application is not clear. So having this quite weakly defined problem, it's hardly possible that someone can help.
You can do the following in order to resolve the issue:
Try to build a minimal test case, which reproduces the problem. Usually you'll need to start with a copy of your source code, and remove features until the bug is not reproducible any more.
After this, you will most likely see yourself, where the problem is.
If not, you can post the example and the changes which make the bug happen. Please kindly try to remove as much as possible from the example, leaving only essential part.
This way you will most likely have your problem solved.
I wrote a console program in c# that takes up to three files as input, and does some data calculations on them.
I'd like to make a simple frontend that allows the user to easily
import files - basically choose up to three files to be routed to the backend code
change settings - I have about 10 settings that I'm currently storing in an app.config file. maybe a simple settings box would be nice
see what's going on - the console program shows some status messages that might be useful to display on a GUI
I have practically no experience with windows forms or GUI design, so I really don't know where to begin. I compiled the backend stuff into a *.dll and am currently playing around in design mode of sharpdevelop...but i really have no idea how to get the two to work together.
any pointers would be greatly appreciated!
The usual pattern, in cases like these, is to make the main features of the application into a class library and call that from a wrapping executable, such as a console app, winforms app or webforms app (if possible). That way you can easily adapt the interface as needed and simply route input and output to and from the class library.
Edit: I realize this isn't a very indepth answer, but I hope it helps to get started at least, together with any other answer that may arrive.
If you want to get started with GUI design in .NET, I recommend you choose WPF (Windows Presentation Foundation). This is the latest technology released in the UI/graphics area by Microsoft and is where everything is heading now. (Windows Forms won't be obsolete for a long time, though it is surely but slowly becoming deprecated.) I noticed however that you are using SharpDevelop, which doesn't yet have real support for WPF (as far as I know), whereas it certainly does for WinForms. If there's any chance you can use Visual Studio, I recommend you begin by learning WPF. You have the advantage of not being confused by previous experience with the styles and methodologies of WinForms, so it would very much be the right way to go.
Whichever you wish to learn, the Getting Started page of WindowsClient.NET (the official MS site for both WinForms and WPF) would be a great resource. There's also a few MSDN articles on getting started with WPF.
Hope that helps.
Have you tried Visual Studio Express editions? They're free and come with a designer for either WinForms or WPF applications.
As a first pass you'll need 3 text areas for the filenames, with associated buttons to bring up the file open dialog (it doesn't actually open the file just returns the filename).
A label to display the status - updated from your worker code.
Then either the various radio buttons, check boxes etc for your configuration settings.
Oh and don't forget the "Start" button to set off your process.
If your process takes a while you ought to use a background worker thread. You can then implement a "Cancel" button to safely abort the process and tidy up if it goes wrong.
There will be optimisations and reorganisations that you can do once you've got it working.
Your question is quite indistinct. If you're asking about working with GUI, you should read some book on Windows Forms.
And if you're asking about how to put your dll in your new windows forms application, then you should just add a reference to it in winforms project's properties and then use classes from dll's namespace.