Cool, no issues. It points to a null parameter in the debugger. But the same code, when executed with just an image add and retrieve (a new c# project), the application works really well. I am unable to determine what is the problem here
So you need to find out why mst is null at this point. Your code is assuming that you always get a valid byte array from r (whatever that is), and hence a valid stream. However, if either of these commands do not return the expected result you are going to have a problem which you are not catering for. You should never assume that method calls like this will always succeed; add some error checks so you can diagnose it properly when it fails.
One of these days I'm going to think of a really clever signature.
I have a form that has an array of text boxes dynamically added to a splitcontainer on a form. I use the same array to add text boxes to the form twice (different data for different table). I would like to use an event handler, preferably once, to change background color to yellow when textbox[i] receives focus, and back to white when it loses focus. I am currently going around in circles. Can anyone help me? Thanks for your input
Add in a lambda, at the point where you create the textboxes. Like the example below;
var tb = new TextBox();
tb.GotFocus += delegate (object s, EventArgs a)
(s as TextBox).BackColor = Color.Red;
tb.LostFocus += delegate(object s, EventArgs a)
(s as TextBox).BackColor = Color.Green;
I am rewriting a desktop application in VS2010 that was written in .Net 1.1. While doing so, I decided to add a couple of features to the app. One is a data source for a drop down list. I am using a local database file (.sdf) for the data.
I noticed in the <namespace>.Properties.Settings file that the connection string is a hard link to where I entered the file location (which is C:\Users\<username>\Documents\db\<filename>). I need this to be more dynamic, due to the fact this app will be on many different computers.
I tried editing to :
But I receive the following error at compile time:
Error 1 An attribute argument must be a constant expression, typeof expression or array creation expression of an attribute parameter type C:\Users\brian\AppData\Local\Temporary Projects\latefeedisc\Properties\Settings.Designer.cs 29 68 latefeedisc
// This code was generated by a tool.
// Runtime Version:4.0.30319.544
// Changes to this file may cause incorrect behavior and will be lost if
// the code is regenerated.
You aren't supposed to modify that file. You should set the property in the constructor of your window.
Don't. It wasn't "ignorant", just overlooked some semantics that "could" give a hint.
It's a real settings-file; now, if only the database-name (or path) is going to differ, it'd might be neat to use a connection-string with a literal set of characters in the place where the databasename should be, and to Replace the literal with the actual path just before using the string.
So, you want the system to do a simple literal replace for you, but you want to roll your own config file implementation? Clever . Are you also going to write all the cool stuff that you get for free with config files such as encryption, versioning, editing through a simple GUI in VS, backwards compatibility, etc?
How do you integrate with the Visual Studio designer?
Configuration files via the designer? Myself I absolutely despise that. Every time you touch it it re-writes the file. Which means that all formatting is lost. And all documentation.
So you have a file that is intended to be manually edited not using VS which has no formatting and no documentation. And which isn't even necessarily guaranteed the have the same ordering between point releases.
It does mess up the formatting, I'll agree with that. Since it's an XML file, I just hit the "Format Document" button and it fixes it. Not enough of an annoyance to give up the designer editor IMO.
And all documentation.
You put documentation in your config file? Thats an extremely odd place for documentation seeing as the .config files are NOT meant to be edited manually by end users. They are meant to be edited by people who know what the settings are (i.e. developers, etc).
guaranteed the have the same ordering between point releases
Last time I checked, XML and .config files were unordered formats. If you are relying on the order of tags in an XML and/or .config file... "ur doin' it wrong".
You put documentation in your config file? Thats an extremely odd place for
documentation seeing as the .config files are NOT meant to be edited manually by
end users. They are meant to be edited by people who know what the settings are
(i.e. developers, etc).
No idea what kind of "end users" you have but my end users are Operations and Support personnel. And they are specifically the people that need to edit the configuration values.
Also no idea how you release software but busienss needs often drive new feature releases along, of course with bug fixes. And those can all require configuration values. So changes happen frequently.
Also although it might be nice to have a formal operations manual actually producing that seems to be a problem at most places I work at. And configuration files that have more than just a couple entries require documentation. Which either means putting it in the configuration file or putting it in another file. If it is put in another file then Operations/Support must be told about it. Repeatedly.
And of course to create a actual operations manual means that I, and no one else, would need to produce the documentation in the first place. Far as I am concerned since I know Operations/Support will be looking to the file anyways the documentation that is in there is going to be the source for the formal document anyways.
Last time I checked, XML and .config files were unordered formats.
Both of those are entirely incorrect.
XML can be unordered or ordered.
And MS config files have some sections that require specific ordering.
But that doesn't have anything to do with what I am talking about...
If you are relying on the order of tags in an XML and/or .config file... "ur
doin' it wrong".
If if fact that had anything to do with delivering a configuration file then you would in fact be correct. But it doesn't.
The order however does matter when Operations/Support uses standard difference tools to compare configuration files. Such as what they might do when they need to install a new major version or point release and they want to insure production machines have the same values with a new configuration file and the old one.
Last Visit: 31-Dec-99 18:00 Last Update: 26-May-17 16:58