divil

People often post questions in the language specific forums when they are not language specific at all. Those forums are for language syntax issues, and language syntax issues only. Therefore, the thread gets moved to its appropriate location and the title is usually altered to reflect the poster's preferred language for replies. However, not everybody knows the syntax of every language so sometimes an answer might be given in another language. Since we're dealing with the .NET framework here, the method will be the same only using different language syntax. An answer in the wrong language is better than no answer at all.

Weird, it worked for me. What is the error you are getting?

You're not defining an absolute path. When VS builds your project, it is copying the DLL to reside in the same folder as the EXE file. .NET executables look for assemblies in the same directory as themselves, then any configured subdirectories, then in the GAC (global assembly cache).

You haven't used the code I posted. Your rect structure has longs in it instead of integers which it should have.

If you don't want to use GDI+, why are you using .NET?

You need to make a TypeConverter for your Appearance class that derives from ExpandableObjectConverter. You link the two together by sticking a TypeConverterAttribute on the Appearance class.

You want the appearance property of your first class to be expandable in the property grid?

I split this off because it belongs in its own thread. You might find the below thread helpful: http://www.xtremedotnettalk.com/showthread.php?s=&threadid=72164

Can you post the whole code, including all your declares.

The StructLayoutAttribute class lets the framework know how to lay your structure out in memory when it's marshaled to an unmanaged application. The vast majority of times you can just specify Sequential, but some people prefer to enter the offsets manually. You also had to change the ByVal to ByRef, because you want to pass a reference to your existing structure instead of just a copy.

mailto:address@domain.com?subject=mysubject&body=mybody

That looks like the correct way to implement mdi forms.

There is no .NET tooltip wrapper for implementing regional tooltips for a control. When I had to implement them in my toolbar control I had to use the win32 api tooltips through platform invoke, there is a fair amount of information in msdn on getting them working. If you get stuck, post in this thread and I'll help.

I think he's trying to get the window bounds of a window outside his application. Public Declare Function GetWindowRect Lib "user32" Alias "GetWindowRect" (ByVal hwnd As IntPtr, ByRef lpRect As RECT) As Integer <StructLayout(LayoutKind.Sequential)> _ Public Structure RECT Public Left As Integer Public Top As Integer Public Right As Integer Public Bottom As Integer End Structure Those are the correct declares.

Isn't Outlook expecting an ActiveX control?

.NET code access security prohibits things running from network shares from performing several types of functions, including disk and database access. To grant permission, go to Control Panel -> Administrative Tools -> .NET Framework Configuration. Choose Configure Code Access Security, then Adjust Zone Security. Increase the Local Intranet zone to full trust.

You can't make ActiveX controls with any of the .NET languages. The closest you'll get is embedding a Windows Forms Control in Internet Explorer, which works quite well if you have the right security set up, and there are several articles online on the subject.

Check out the Screen class. Using it you can get coordinates of all screens present and display your form on whichever you like.

Why do you need it?

You're right, there is no Flexgrid replacement in .NET. Sometimes you might be able to use a datagrid in place. I hear there is a good .NET flexgrid at http://www.componentone.com .

There is nothing to explicitly make a function get inlined, but if optimizations are turned on and the compiler things there is something to be gained from doing it, it very likely will.

If you're using ShowDialog to show it, that procedure will halt until the dialog is closed, so the next thing to execute will be the next line of code after the call.

http://www.syncfusion.com/FAQ/WinForms/FAQ_c89c.asp#q804q The common answer to this seems to be looping through the selection one character at a time.

You won't find help from this forum on disabling windows file protection.

The main difference between the .NET treeview and previous versions is that you only add top-level nodes to the treeview itself. All other nodes are added to the Nodes collection belonging to their parent node.