mocella

Have you run "vsvars32.bat" yet? (C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\Tools) This should let NANT find CL.exe - that's what I posted that link for in your last thread. Let me know if that fixes it.

Do you have VS2002 installed on your machine? Not sure if it matters, but it looks like the CL-Task expects CL.exe version is the one from VS2002, not VS2003. From the Nant Site: This task is intended for version 13.00.9466 of cl.exe. The versions of CL.exe are VS2002: 13.00.9466.0 VS2003: 13.10.3077.0 This link may help: http://www.mail-archive.com/nant-users@lists.sourceforge.net/msg04916.html Beyond this, I'm pretty unsure of how to tell you to proceed. Sorry

The file you're looking for is either at C:\Program Files\Microsoft Visual Studio .NET\Vc7\bin or C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\bin You'll have to update your Nant.exe.config to know where to look, etc.

You can write your own java compiler task with the Nant-Contrib stuff. Again though, I'd probably just use each tool for it's intended purpose - Ant for JAVA and NANT for .net stuff. http://sourceforge.net/projects/nantcontrib/

Have you looked in your Event Viewer to see if anything is written there? Have you tried to compile from the command-line? I'm not sure if there is a debug file generated from VS.net when it crashes, but I'd imagine there's something on your drive detailing the crashes. Perhaps someone else here knows about that? Oh, and have you tried rebooting your machine since this started :rolleyes:

In C# it looks something like this: this.btnTest.Click -= new System.EventHandler(this.btnTest_Click); That will turn off the click event handler for "btnTest", and to turn it back on, you'd do this (notice any similarities to the first code?): this.btnTest.Click += new System.EventHandler(this.btnTest_Click);

Not sure why it wouldn't show up. I've always just used an image file for my WinForms buttons for arrows. There's some basic ones in the "C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\Graphics\icons\arrows" folder (assuming you have VS2003 and installed to default location). Not exactly answering your question, but it's how I've handled this problem....

Create a second ReadData(ByVal varSQLString As String, sqlParamArray() As SqlParameter) This way, you only create one overload for your function and you can pass as many params as you want and of all types and directions and not have to worry about it. This is right from MSDN - they also show an invalid paramaters adding as one line of code, but that's not supported: Public Sub CreateMySqlCommand(myConnection As SqlConnection, _ mySelectQuery As String, myParamArray() As SqlParameter) Dim myCommand As New SqlCommand(mySelectQuery, myConnection) myCommand.CommandText = "SELECT CustomerID, CompanyName FROM Customers WHERE Country = @Country AND City = @City" myCommand.UpdatedRowSource = UpdateRowSource.Both myCommand.Parameters.Add(myParamArray) 'this does not work!!!!! Dim j As Integer For j = 0 To myCommand.Parameters.Count - 1 myCommand.Parameters.Add(myParamArray(j)) Next j Dim myMessage As String = "" Dim i As Integer For i = 0 To myCommand.Parameters.Count - 1 myMessage += myCommand.Parameters(i).ToString() & ControlChars.Cr Next i Console.WriteLine(myMessage) End Sub

Looks like you have to use Shell32.dll for this: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/shellcc/platform/shell/reference/ifaces/itaskbarlist/itaskbarlist.asp

Okay, I was thinking the menu-bar, not the window's taskbar. Here's what I dug up in Google Groups - haven't tried it, but it seems logical: Dim m_oTB As New TaskbarList Private Sub Form_Activate() m_oTB.ActivateTab hWnd End Sub Private Sub Form_Load() m_oTB.HrInit m_oTB.AddTab Me.hWnd End Sub Private Sub Form_Unload(Cancel As Integer) m_oTB.DeleteTab hWnd End Sub

It sounds to me like what you'll need to do is create a new file-menu item like "Open Windows" and add new menu items and events point to your new child windows as you open said child windows. You'll also have to add cleanup code to remove the menu items as you close the child forms so there's not a chance of null references with displaying a form that is no longer available. To my knowledge, there isn't an automatic means to generate the file menu to reference your child form instances, just good old-fashioned manual code writing. Check out this link, I think it may help you: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vbcon/html/vbtskcreatingwindowlistformdiform.asp

You need to spin through your mdiChildren collection from the mdiParent control and find the open instance form1, or whatever form you wish to bring-to-front.

Check out the BringToFront() method that your child-forms have - that should do the trick.

Perhaps the database connection object is a bad example here - since a static helper class can probably suit those needs as mutant points out. However, for a stateful object - like some datatables (assuming you're not caching) you need in various forms , or session information that is just stored in-memory while the app is running, etc, I'd just assume hold reference to this object in the mdi-Parent, as it is the main entry/exit point for forms in the app.

I don't think I'd leave a database connection open for the duration of an application's lifetime - just open and close it as you use it. You can keep your connection object alive in the mdi-parent form and perhaps create a public property that the mdi-child forms can reference for their data needs, or you can pass a reference of this connection object to the child forms at constructor time. I'm not sure if there's some context object like how ASP.Net does things - but with the mdi-parent you really don't need one - the mdi-parent can act as this "global object server" for all the mdi-child forms.

You didn't mention so I'll ask if you're doing this as an MDI app, or just having a bunch of forms open on the desktop or what. Either way, you can deem one form as the driver (mdiParent if MDI) and have that form create the instances of your objects. Then you can create properties or pass references or several other methods to allow the "child" level screens to have access to those objects.

This littly book has been pretty useful for our coders moving from VB6 to c#, and it's like $10 - http://www.oreilly.com/catalog/csharpvbpr/

IEnumerable should do the trick

The easiest thing here (for consistency anyhow) is to just forget using the web-reference in the VS.net project and add references to your .dlls that WSDL.exe created. This way, your NANT script is using the same .dlls as your VS project.

The dumps are also helpful for the person that can disregard the supplied answers (that are often wrong anyhow) and looking up all the available answers themselves in MSDN and reading up on those topics. This way, the developer has not only read up on the right answer, but several related topics that they otherwise may not have looked into. One site had online tests that people can take and it shows what others answered but it seems like once one person answers the question one way, others just blindly follow, and they're the wrong answers.

You need to create a proxy for your webservice using the WSDL.exe utility. Once you run this, you'll have a dll that you can reference in your command-line compile scipt. Check this link for help: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconCreatingWebServiceProxy.asp

The tests were $125/test at ProMetric centers, and I assume the same at the Vue centers(is that the other?).

No, they cheated people that actually know their stuff and earned their MCAD/MCSD designation. I've been at several clients where they hire some "expert MCSD guru" guy who's at my desk asking how to do very trivial tasks in .net/vb, etc that anyone with a small amount of working knowledge of said subjects wouldn't have to think twice about. Once they see a few of these types of people, they don't even bother looking on a resume for the MCSD, so there's no real advantage when all else equal on two resumes. Sad really.

You can only have one indexed property per class (the "this", which is your indexer). I went through this headache early in the planning stages of my current project, but managed to design compeletly around them for most situations. Here's a pretty decent article I had bookmarked from my earlier searches: http://www.csharphelp.com/archives/archive140.html

You can try using the radioButton.Validating() event - it accepts the cancel-event-args, so in that logic if all is not well, just do "e.Cancel = true;" to cancel the event at that point.