Using SQL Server 2000, does the SQL Reporting tools allow you to output in RTF format?

This morning my VS.NET 2005 crashed on me while at the same time SQLEXPRESS had thrown up (on its own) a command prompt, it was doing something to my file. So I had to kill the entire process because it was not responding. From then on I have not been able to connect to an MDF file. I am able to create new databases on my instance of SQLEXPRESS, my TCPIP and Named Pipes are working, but whenever I try to add an MDF file it times out. In the event viewer I am getting periodic messages about my TCPIP for SQL not being valid, but I don't see how considering I am able to create new databases and the client and the service are configured on the same port. For what its worth, the LOG file does not show SQLSERVER express listening on any ports.

Say I have a project, a windows form project. In it I create one or more UserControl derived controls. I would think they automaticaly show up in the Toolbox, but apparently not. So how do I get them to show up? If i'm creating them within an EXE project (at least in VC++) I am unable to add teh EXE in the choose item when right clicking on the toolbox, so I'm wondering what the steps are to get the control on there in drag and drop fashion, without having to resort to hand coding it? Thx.

Ok, here are the absurd steps I needed to remove it. I had to go to the actual folder where it resided, delete it, relaunch VSS, attempt to open it, then the button was no longer grayed out. Brilliant stuff, I'm glad to see so much work was put into VSS over the past 5 years.:mad::mad::mad::mad::mad:

For love nor money I do not understand why in Visual Source Safe there is a button to remove a database but it's grayed out! I have a database set up on one drive and I want to move it to another. Because I haven't used it yet, I just want to delete it and recreate one with the same name on a different drive. All I can do is chose File> Open Database and then there's a button to remove the current one, but its grayed out. Can anyone shed some light on this latest ingenious UI design from Microsoft?

If I do something like the following: #define #include "XYZ.h" using namespace XYZ; #undef I get the following error: error C2007: #define syntax I get that error withour without the using namespace statement as well. Is that what you meant or was it something else?

Well that might work for my own source code but VC8 includes VC headers that call managed code and make calls to System:: namespace classes. This means I would have to modify all of these Microsoft headers by hand for this to work, which would be impossible to do without causing all sorts of other headaches. Is there not some way to rename a known .NET namespace to another name? Like rename ::System to ::DotNetSystem ?

Well that changed the way the error was thrown, but it looks to be throwing the same error. Here's what it is saying: Managed Debugging Assistant 'LoaderLock' has detected a problem in 'D:\Dev\throwaway\pinvoke\pinvoke\bin\Debug\pinvoke.exe'. Additional Information: Attempting managed execution inside OS Loader lock. Do not attempt to run managed code inside a DllMain or image initialization function since doing so can cause the application to hang.[/code] Here is what my DllMain looks like, but again why isn't this happening with my release version? `BOOL APIENTRY DllMain( HMODULE hModule, DWORD ul_reason_for_call, LPVOID lpReserved ) { switch (ul_reason_for_call) { case DLL_PROCESS_ATTACH: case DLL_THREAD_ATTACH: case DLL_THREAD_DETACH: case DLL_PROCESS_DETACH: break; } return TRUE; }`

I'm getting an exception that looks like below when my debug C# app calls into my debug C++ dll (which uses the MS CRT, debug dll). Apparently if I go to the Menu>Debug>Exceptions>Managed Debugging Assistants and unchecked Loader Lock checkbox, the exception goes away but I get a message saying that I'm trying to use a dll that's loading the CRT without a manifest file. This must all be part of this new manifest side-by-side stuff that is introduced in VS2K5. However I am not getting this problem when I run the release build of my solution and I cannot for the life of me figure out what Microsoft wants you to do here. All I want to do is call into my dll, why has this become so hard to do in the new version of VS.NET ?? Loader Lock was detected: Attempting managed execution inside OS Loader lock. Do not attempt to run managed code inside a DllMain or image initialization function since doing so can cause the application to hang. -- modified at 18:14 Monday 5th December, 2005

Yeah its the same. Actually someone else pointed out to me that my debug dll is probably dependent on the debug dll of the CRT and that it can't find it. So I need to make sure the debug DLL of CRT is in my path. What is the filename of the debug crt DLL?

I'm having a very odd problem. I have a basic C# form app that pInvokes into a C++ dll. When I build my C++ dll and C# app in Release mode, the C# app can load the dll and call into it just fine. However if I build the solution in Debug mode, the C# app throws a DllNotFoundException. I've double checked and the C++ debug version of the dll is being properly copied into the C# app's bin/debug folder, so its actually there. Why is it able to load the release version and not the debug version?:mad:

I am trying to pInvoke into a very simple C++ dll I have created, from my C# winforms app. I start by creating a C++ dll using the VC8 wizard, and checking off "export symbols" as I want to call a basic function from C#. By default the wizard creates a sample function and exports it. However when I run my C# app, it says it can't find an entry point for the function name I have defined in my DLLImport attribute. I have made sure that the dll is in the same directory as my C# executable. Incidentally, I can pInvoke fine into other system dlls, so what am I doing wrong?

I have a VC8 Managed C++ Windows Form project. In it I try to overide thd WndProc like below, but when debugging the function is never called. I'm not sure why, has the method of doing this changed since VC7.1?

void WndProc(System::Windows::Forms::Message MsgByRef)
{
switch (MsgByRef.Msg)
{
case WM_PAINT:
{
PAINTSTRUCT kPS;
HDC hDC = BeginPaint((HWND)MsgByRef.HWnd.ToPointer(),&kPS);

                    EndPaint((HWND)MsgByRef.HWnd.ToPointer(),&kPS);

		}
	}

	Form::DefWndProc(MsgByRef);

}

Alright I tried to simply add XYZ:: to all instances of System in the headers of the 3rd party library , but I realized that the problem is with microsoft's yvals.h usage of System.bla.bla when I've included XYZ as a namespace. It's not working. I am going to have to rename and rebuild the entire 3rd party library, and everything that uses it.. What a major pain in the neck.

Thanks, the 3rd party library is actually a static lib but I do have the source to it. So I guess I can go through it and do a replace on "System" to make it "XYZ::System". Is it possible to use #import on a .lib file? That would be easier but I guess its not that big a deal, one find and replace should do the trick.

I have a C++ app that includes a 3rd party library that has a type called 'System'. This class exists in a namespace, let's call it XYZ::System. Then I am compiling my C++ app with /clr and somehow when VC8 includes xlocale (which in turn uses a macro defined in yvals.h) that calls a method in .NET (System.bla.bla) there is an ambiguity. How can I resolve this easily?

I have a C++ app that includes a 3rd party library that has a type called 'System'. This class exists in a namespace, let's call it XYZ::System. Then I am compiling my C++ app with /clr and somehow when VC8 includes xlocale (which in turn uses a macro defined in yvals.h) that calls a method in .NET (System.bla.bla) there is an ambiguity. How can I resolve this easily?

I am considering a situation where I have (n) number of form windows, each with an instance of the Microsoft Web Browser Control (IE) on each form. In each web browser control is an HTML page that has a Java applet. This is the only way I am aware of to get a Java applet to paint within a .NET Forms window. Given that scenario I am trying to determine whethere there would be one Java VM loaded for all of the (n) applets inside the (n) MS Web Controls? Or would there be one Java VM loaded for each applet? Also, if using IE6, what JVM is being used? Microsoft's or Sun's? Also, are there any thoughts on what overhead there would be in having multiple instances of the MS Web Control? I am expecting upwards of 10-15 as a worst case.