divil
*Gurus*
-
Posts
3026 -
Joined
-
Last visited
Content Type
Profiles
Forums
Blogs
Events
Articles
Resources
Downloads
Gallery
Everything posted by divil
-
It's very uncommon, and I can't think of many examples. One is the designers adding a GridSize property to things like Panels though.
-
Splitters work with the z-order of controls on the form. If this is somehow wrong, you should first right-click the control you want on the left of the splitter and bring it to the front, then bring the splitter to the front, then the control you want on the right.
-
If you remind me at the weekend I might just have a little more time then.
-
MustInherit in VB is the same as abstract in C#. The designer has to create an instance of the base class in order to design it, so unfortunately there's no way around this well-known issue except the hack Nerseus suggested.
-
Environment.CommandLine
-
Personally I use XML files. INI hasn't been a recommended means of storing settings since Windows 3.1, and .NET's xcopy deployment mindset lends itself to XML files more than it does to using the registry.
-
The changes should be being made, I don't know why they're not. Every time you run your solution an exe is made and that is what's run.
-
Standard edition doesn't have the upgrade wizard, but that shouldn't concern you since it's a pile of rubbish. It also doesn't let you create DLLs, which severely limits the extensibility of what you can do. Also as somebody already said, the Server Explorer is limited. I wouldn't settle for less than pro.
-
That method allows you to add properties to the object you are designing, from the designer. In other words, design-time only properties.
-
You need 25 posts before you can set an avatar.
-
Concat is a static method of the String class, so even when you were calling msg->Concat, you were really just calling the static one which obviously doesn't modify any source string.
-
The resx file is *already* embedded in your solution. VS.NET converts it to a .resources file whenever it builds the project. This conversion isn't something you do in your program, it's something you'll want to make another program to do if you're trying to build the solution from the command line.
-
It sounds like you need an OpenFileDialog or SaveFileDialog.
-
I don't know of one. Use the help to examine the methods of those two classes, use one to read and one to write each resource in the files. It's not trivial.
-
When you have binary resources in your form (pictures, icons etc) the command line gets more difficult. You will need to manually convert the form's .resx file in to a .resources file using the .net framework classes ResXResourceReader and ResourceWriter. Then you can use the /resource command line parameter to specify each resource file to embed in the file. The filename IS important - I think it should be the root (or default) namespace of your assembly plus the form name, separated by a period. Or you could purchase a non-crippled version of VS.NET which does it all for you :)
-
It works the same. Forms are just classes, after all.
-
Check out Environment.TickCount
-
.NET executables are not native code, they're mostly IL (Intermediate Language). You make use of the enormous .NET framework from your application to get things done, you're going to have to package it too. You can still windows apps in plain C that don't require any dependancies (except windows itself).
-
Personally I would just set the CharacterCasing property to Upper :P
-
You can't I'm afraid.
-
MessageBox.Show("First line" & Environment.NewLine & "Second line")
-
If you give your application a manifest file, Windows XP will theme all the controls on it properly.
-
The point of setting Flatstyle to System is that the system assumes all drawing responsibility for the buttons, so I'm not surprised that you can't override those events and achieve anything. You should try subclassing WndProc and looking for the WM_PAINT message.
-
I've seen other people ask for this too, I don't know why though. Inheritance is designed so you can extend or replace functionality on a base class, not remove it. If that were the case, you could no longer assume that a derived class has a method that a base class had and things would get very nasty.
-
You don't have to perform any check, every control has a Controls collection you can enumerate through to get access to its subcontrols.