divil

You'll need to be a little less vague before we can understand what you're trying to accomplish.

Your help file can. Interfaces, like classes, define a set of properties, methods, and events. But unlike classes, interfaces do not provide implementation. They are implemented by classes, and defined as separate entities from classes. An interface represents a contract, in that a class that implements an interface must implement every aspect of that interface exactly as it is defined. With interfaces, you can define features as small groups of closely related members. You can develop enhanced implementations for your interfaces without jeopardizing existing code, thus minimizing compatibility problems. You can also add new features at any time by developing additional interfaces and implementations. Although interface implementations can evolve, interfaces themselves cannot be changed once published. Changes to a published interface may break existing code. If you think of an interface as a contract, it is clear that both sides of the contract have a role to play. The publisher of an interface agrees never to change that interface, and the implementer agrees to implement the interface exactly as it was designed. [mshelp]ms-help://MS.VSCC/MS.MSDNQTR.2002APR.1033/vbcn7/html/vaconInterfacesInVisualBasic70.htm[/mshelp]

No.

The PropertyGrid control in the IDE is part of the framework and easy to use in your own applications. Go to Customize Toolbar, click on the .NET tab and it will be in the list for you to check. I don't know why it isn't checked by default, but it isn't.

Private Sub Panel1_Paint(ByVal sender As System.Object, ByVal e As System.Windows.Forms.PaintEventArgs) Handles Panel1.Paint Dim b As Brush b = New Drawing2D.LinearGradientBrush(New Point(0, 0), New Point(0, Panel1.Height), Color.Red, Color.Green) e.Graphics.FillRectangle(b, Panel1.ClientRectangle) End Sub

It's not going to be in VS.NET 2003, perhaps in VS.NET Yukon.

I suggest you look at this file: FrameworkSDK\Samples\Technologies\Interop\PlatformInvoke\ReadMe.htm It contains information on how to marshal arrays to win32 dlls like you are trying to do, specifically arrays of integers. There is a sample project included in a subdirectory, doing exactly this.

XP menus by default are drawn a pale white colour in the background, but apart from that don't look much different from menus in previous versions of Windows. XP toolbar controls are themed with a gradient background and smooth bevels on the buttons, but do not look like Office XP widgets. Here's a quick snapshot I took of XP menus with the default Luna theme, I find it surprising your school has a theme which makes XP widgets look like Office XP ones.

My suggestion would be to expand on dynamic_sysop's suggestion by making that boolean variable a static ("shared" in vb.net) member of the form class. Then in the form's constructor you could set it to true, and check it before creating a new instance of the class.

No. The closest you'll come is drawing it entirely by yourself.

No they don't. XP style and Office-XP style are quite different. The image he posted shows the kind of menus that are present in Office XP and Visual Studio .NET. Normal menus and toolbars in Windows XP do not have this look.

I've never heard of that control. Are you sure you don't mean mswinsck.ocx?

From your own comments: ' Notice that the signature of this event is different from usual, as it ' is expected to return a Boolean - if false the default effect associated ' with the event (for example, jumping to another page if the click is on ' an hyperlink) is canceled. Surely that means if you Return True at the end of that function the browser will do the default action for these things? I had to remove your attachment because it contained executables, can you post it again without?

Try the Enter and Leave events.

I have no idea why this would happen, but my first course of action would probably be to uninstall and reinstall visual studio.

I downloaded it but it says it's a trial version and wouldn't run at runtime. However at design time I did notice that it's not a control container, and the fact that it's an ActiveX control really doesn't help either. I don't know what to suggest, apart from not using ActiveX controls :) Robby, the parent was as you thought (Label1.Parent = PictureBox1)

Here's a code example for something that compiles a file on disk, adding references, to a Windows exe file. Dim c As CodeDom.Compiler.ICodeCompiler Dim p As New CodeDom.Compiler.CompilerParameters() Dim r As CodeDom.Compiler.CompilerResults Dim err As CodeDom.Compiler.CompilerError c = New Microsoft.VisualBasic.VBCodeProvider().CreateCompiler() 'Set up compiler parameters here p.ReferencedAssemblies.Add("System.dll") p.ReferencedAssemblies.Add("System.Drawing.dll") p.ReferencedAssemblies.Add("System.Windows.Forms.dll") p.GenerateExecutable = True p.OutputAssembly = "c:\out.exe" p.CompilerOptions &= "/t:winexe" p.MainClass = "form1" 'Compile r = c.CompileAssemblyFromFile(p, "c:\file.vb") 'Analyse results If r.Errors.Count <> 0 Then 'Show errors For Each err In r.Errors Next End If 'Do something with compiled assembly (r.PathToAssembly)

A quick test I knocked up -

I know it had a gradient background, and my way works. I tested it, putting my label in a picturebox with the screenshot you posted as a background. Remember, you won't get the effect at design time, only at runtime after you set the .Parent property.

You're not running on Windows 9x are you? I know it doesn't support the FileSystemWatcher class.

This is surprisingly easy to do. At runtime, in your Form_Load, stick this: Label1.Parent = PictureBox1 Replacing PictureBox1 with whatever the name of your tab control is. The label will then get its background from that, assuming its backcolor is set to transparent.

Have you tried not setting VScroll and HScroll at all?

No. Sorry :) If you have a specific question I will do my best to answer it.

Please post all the relevant code you have so far, and exactly what requirements you have with regards to referencing assemblies and imports statements in the compiled assembly. Also what language you are targetting.

This piece of code adds up all the numbers in the second column on a listview in Details mode. Dim l As ListViewItem Dim count As Integer count = 0 For Each l In ListView1.Items count += Integer.Parse(l.SubItems(1).Text) Next MessageBox.Show(count.ToString())