I've got a web app that uses the Microsoft remote scripting engine to run some ASP script on the server. This application works fine and has always worked fine without any version of the JRE installed. If I install the JRE version 1.3 (English edition) this application still works fine. If I install the JRE 1.3 (international edition) the remote scripting no longer works. Does anybody have any idea why installing the international JRE would hose my remote scripting?

I've seen this issue noted a few other places on the web, but so far no good solutions have been found. I have an XSL file I'm using to transform some XML. This XSL file has existed for a long time now and has always worked on version of IE <= 5.5. Some of our clients are now moving to an IE6 environment and I've found that the new version of the XML parser included with IE6 messes up when performing the transform. Specifically, when the transform attempts to output a textarea block, with code similar to this:

<xsl:attribute name="FIELD_TYPE">s</xsl:attribute> <xsl:attribute name="DATA_TYPE">T</xsl:attribute>

The closing textarea tag is never output to the HTML when using the XML parser included with IE6. In IE <= 5.5 however this works just fine. Has anybody else experienced similar problems, or have a suggestion for a solution? It would be appreciated! Thanks!

Is there a way to define an assignment operator on a managed C++ class? I tried using the C# syntax, but that doesn't seem to want to work... What I've got (that isn't working) is something like this: public __gc class ATTRIB { ATTRIB(); ATTRIB(const ATTRIB* a); virtual ~ATTRIB(); static implicit operator ATTRIB(ATTRIB* a) { return new ATTRIB(a); } }

Thanks for the good information... but is there a way I can convert to an unsafe type BEFORE actually passing the data into a function? If I've got a String* or Stringbuilder* in Managed C++ and want to convert it into an unmanged type like char* or LPStr, how is that possible? -dvryce

I have a class that has been written in plain C++ that makes calls into a library that exports many functions that take char array parameters. What I want to know is how I can get / convert the data in a .NET String object into a plain char array so that I can pass the value into the function call? Basically any help converting the new .NET types into older style "unsafe" types would be helpful. Thanks.

Is there an easy way to maximize a winform at runtime? For instance, by setting a property instead of getting the screen dimensions and then specifying the size manually?

I've read them all so far an I agree that Jordan was a great writer up to about book five. Then things went downhilll and the books became mainly "filler". Book nine had some good stuff to the end (i.e. thank god for Rand finally *DOING* something) but it still lacked much content. Hopefully the series will pick up again before the end.

Neill Jordan wrote: I just did a quick test and the following exception was thrown - System.Exception: A form can't be both an MDI child and MDI parent. So, if it is possible, it isn't done in the most obvious way. Yeah, I did get this far... Thanks for the attempt though. It sure as hell wasn't easy under MFC so it probably isn't easy this time around either. I guess this is a good indication that I should rethink my GUI design! :-D

>(printers are OK, but computers are not) Maybe the high-end printers are ok, but I've had two HP inkjet's fail on me in under a year. I find it hard to believe that I simply got defective units both times. >or order from Gateway, Dell, or some other computer maker that has good parts, good service, >and full support. Gateway's used to be good a few years ago, but nowdays I wouldn't trust the components they use as far as I could throw them. Since the push to do everything "on motherboard" the quality has gone waaay down. Even Dell uses cheaper components these days than they used to in efforts to reduce costs. Dell is still an acceptable option, but have to agree that building your own system is *the best* way to go. It's really not all that difficult, even for someone with limited technical knowledge once you do a little research. This way you get everything exactly as you want it, and YOU not the OEM get to choose what components (if any) you want to save money on and what components you want to go all out on.

Is there a way to make a form show up as both an MDIChild and an MDIContainer? That is to have a top level window with sub-windows each of which has it's own sub-windows? I managed this once in C++ with MFC through a method much to complicated to describe here, but I'm totally new to C# and wondering if this is possible?

It's having the problem when the Visual basic DLL attempts to make the call into the VC++ DLL. For some reason this call is not taking place on the Win9x machine, but on the NT/2k machine it works fine. The visual basic declaration of the VC++ dll function looks like this: ' Declare VC++ DLL function import Declare Function IndexMsg Lib "OL_Index" Alias "IndexMessage" (ByVal msg_path As String, ByVal msg_note_path As String) As Integer The actual call to this function looks like: ' Call VC++ DLL function to start the import process result = IndexMsg((temp_path + MAIL_NAME), (temp_path + MAIL_NOTE_NAME)) On the VC++ side of things, the function declartion looks like: extern "C" UINT IndexMessage(LPSTR msg_path, LPSTR msg_note_path); And the implementation like: extern "C" UINT IndexMessage(LPSTR msg_path, LPSTR msg_note_path) { AFX_MANAGE_STATE(AfxGetStaticModuleState()); // debug call to see how far the call goes AfxMessageBox("Made it into Index func!", MB_OK); // call the function to perform the indexing tasks return theApp.DoDisp(CString(msg_path), CString(msg_note_path)); } And finally my .DEF file for the VC++ DLL exports looks like: LIBRARY "OL_Index" DESCRIPTION 'OL_Index Windows Dynamic Link Library' EXPORTS ; Explicit exports can go here IndexMessage @59 PRIVATE

I've got a COM addin DLL written in VB6 for Outlook2000 that makes calls into an MFC regular DLL written with VC++6. On both WinNT and Win2k this works fine. However when trying to run the application on a Windows 9x machine the VB6 part of the application works fine up to the point where it attempts to make the call into the VC++ DLL. I believe I have all the necessary dependencies copied to the proper location on the Win 9x machine and I am not using any NT specific code so I am stumped as to why this will not work. Anybody have any ideas for me?

Yeah, back in the day I used to be pretty into D&D though I've always liked Earthdawn *much* better. In my D&D days I started off with a human cleric, but then the 'lawful good' alignment got to be too much of a pain in the ass for me to follow so I created a new character that was much more to my liking. It was an elf warrior / magic user dual class character. I think I got him up to about level 24 before I retired him because he got to be just TOO good. For the last several levels of his lifetime he was in possession of a sword named "Shieldbreaker" that basically made him unstoppable. The sword kind of had a mind of it's own in that whenever he attempted to use it, it drove him into a battle lust causing him to be heedless of his own injuries. Granted the sword could slice through most armor and weapons like a hot knife through butter, but this in itself sometimes became a problem. I fondly remember one time wading into a sea of about 30 fire giants and cutting them all down single-handedly. Granted I broke near every bone in my body and lost most of my blood, but hey that's why you always keep a cleric in reserve! :-D

Just solved my own problem... The answer was to be found in some comments containing the code for the AfxOleInit() call. I had to calle OLEInitialize() before doing anything else in my app's InitInstance() and now it all works fine. Why calling AfxOleInit() doesn't have the same affect is beyond me, but hey, that's just the way it works! :-D

I'm not an MFC newbie and I'm still having the same exact problem with a different ActiveX control. I've been told that you also need to make a call to AfxOleInit() in the DLL initialization, but I've done that and it hasn't helped me a bit. Nobody so far has been able to help me solve this problem and it's really becoming frustrating. Let me know if you find a solution.

I am making sure to call AfxOleInit() and AfxEnableControlContainer() in my App's InitInstance. Then in the constructor for my dialog I create a new object of the ActiveX control type which I then call the Create() member on in the dialog's OnInitDialog() function. For some reason after the call to create the control object's HWND is still NULL. It keeps failing on an assertion error in "Winocc.cpp" which I think is a result of trying to call a method on this object with a NULL hwnd. The error as reported by the VC++ debug window is as follows: Loaded 'C:\WINNT\system32\OLE32.DLL', no matching symbolic information found. CoCreateInstance of OLE control {B2D168E0-5597-101D-843A-DA16297B4C87} failed. >>> Result code: 0x800401f0 >>> Is the control is properly registered? I'm pretty sure the control is registered however as I ran a successful call to regsvr32 on it.

I'm having the same problem with a different ActiveX control I'm using in a modeless dialog from within a DLL. For some reason it seems as though the ActiveX control is not being created properly during the call to Create(). Mine always has a NULL hWnd after the call to create so whenever a method on the control object gets called it bombs out with that same assertion error you're getting because the control has actually not been created properly. I wish I had a solution for you, this one is driving me crazy!

I have a very particular problem that I need some help with. My problem is that I am creating a regular MFC DLL that displays a dialog which then does some work based on user input. I need to create an ActiveX control (in this case Snowbound Software's Rastermaster OCX) on this dialog at runtime. No matter how I've tried to approach this problem it just does not seem to want to work. It seems to bomb in the InitControlContainer() function in the MFC source file OCCCONT.CPP, where it goes to make the call to m_pCtrlCont = afxOccManager->CreateContainer(this); I've tried this using other ActiveX controls and have gotten the same problem so I do not believe it's a problem with the snowbound control in particular. Can anyone please tell me if I'm just doing something wrong, or if what I'm attempting to do is just simply not possible? Any help will be GREATLY appreciated! Thanks! :confused: X 10