badone

As of this morning following these updates last night;

Security Update for Microsoft .NET Framework, Version 2.0 (KB928365)

Security Update for Microsoft .NET Framework, Version 1.1 Service Pack 1 (KB928366)

Code that compiled just fine a couple of days ago now causes the following

1>------ Build started: Project: tsapi_form_test, Configuration: Debug Win32 ------

1>Compiling...

1>tsapi_form_test.cpp

1>c:\working\visualc++\projects\tsapi_form_test\tsapi_form_test\Form1.h(36) : fatal error C1001: An internal error has occurred in the compiler.

1>(compiler file 'msc1.cpp', line 1392)

1> To work around this problem, try simplifying or changing the program near the locations listed above.

1>Please choose the Technical Support command on the Visual C++

1> Help menu, or open the Technical Support help file for more information

1> This diagnostic occurred while importing type 'System::Runtime::InteropServices::InvalidOleVariantTypeException ' from assembly 'mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'.

1> This diagnostic occurred while importing type 'System::Runtime::InteropServices:llImportAttribute ' from assembly 'mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'.

Line 36 is the call to DllImport

#pragma once

namespace tsapi_form_test {

using namespace System;

using namespace System::ComponentModel;

using namespace System::Collections;

using namespace System::Windows::Forms;

using namespace System:ata;

using namespace System:rawing;

// For DllImport

using namespace System::Runtime::InteropServices;

/// <summary>

/// Summary for Form1

///

/// WARNING: If you change the name of this class, you will need to change the

/// 'Resource File Name' property for the managed resource compiler tool

/// associated with all .resx files this class depends on. Otherwise,

/// the designers will not be able to interact properly with localized

/// resources associated with this form.

/// </summary>

public ref class Form1 : public System::Windows::Forms::Form

{

public:

Form1(void)

{

InitializeComponent();

//

//TODO: Add the constructor code here

//

}

private: [DllImport( "CSTA32.DLL", CallingConvention=CallingConvention:tdCall )]

static int acsOpenStream(

ACSHandle_t FAR *acsHandle,

InvokeIDType_t invokeIDType,

InvokeID_t invokeID,

StreamType_t streamType,

ServerID_t FAR *serverID,

LoginID_t FAR *loginID,

Passwd_t FAR *passwd,

AppName_t FAR *applicationName,

Level_t acsLevelReq,

Version_t FAR *apiVer,

unsigned short sendQSize,

unsigned short sendExtraBufs,

unsigned short recvQSize,

unsigned short recvExtraBufs,

PrivateData_t FAR *priv);

Now this app. has had quite a bit of work done on it and I have an example program running downstairs that does a screen pop on an incomming phone call so, as you can imagine i wouldn't have gotten very far if these calls to dllimport had been causing internal compiler errors all along :-P

I intend to roll back the security updates to verify the problem but thought I would post here in case it helps anyone else in the same boat. Will post results if I get no immediate feedback here.

Microsoft Visual Studio 2005
Version 8.0.50727.42 (RTM.050727-4200)
Microsoft .NET Framework
Version 2.0.50727

Installed Edition: VC Express

Microsoft Visual C++ 2005 76542-000-0000011-00125
Microsoft Visual C++ 2005

XP Pro service pack 2

Creating temporary file "c:\working\visualc++\projects\tsapi_form_test\tsapi_form_test\Debug\RSP00000138401180.rsp" with contents
[
/Od /D "WIN32" /D "_DEBUG" /D "_UNICODE" /D "UNICODE" /FD /EHa /MDd /Yu"stdafx.h" /Fp"Debug\tsapi_form_test.pch" /Fo"Debug\\" /Fd"Debug\vc80.pdb" /W3 /c /Zi /clrure /TP /FU "c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.dll" /FU "c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Data.dll" /FU "c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Drawing.dll" /FU "c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Windows.Forms.dll" /FU "c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.XML.dll"

".\tsapi_form_test.cpp"
]
Creating command line "cl.exe @"c:\working\visualc++\projects\tsapi_form_test\tsapi_form_test\Debug\RSP00000138401180.rsp" /nologo /errorReportrompt"


Re: Visual C++ Language Internal compiler error

einaros

Please report this at http://connect.microsoft.com/VisualStudio.




Re: Visual C++ Language Internal compiler error

badone

Thanks for the suggestion einaros.

I consider myself a reasonably intelligent and web savvy individual but I'm afraid posting a bug on the "connections" site is beyond me. I log in with my hotmail credentials, it gives me no option to apply to the Visual Studio and .NET Framework connection yet when I go to post a feedback/bug report it tells me "You need permission to submit feedback in this area. To apply for permission, browse through your choices on the Available Connections page. "You need permission to submit feedback in this area. To apply for permission, browse through your choices on the Available Connections page." and I go around in a big circle. I feel like Chevy Chase in Eurpean Vaction.... "Look kids, Big Ben, Houses of Parliament". I feel like a sap but can anyone tell me the trick

Cheers,

badone





Re: Visual C++ Language Internal compiler error

einaros

Create an account, navigate to https://connect.microsoft.com/availableconnections.aspx, scroll down to the very bottom of the page and hit "Apply" next to Visual Studio connection.




Re: Visual C++ Language Internal compiler error

badone

einaros wrote:
Create an account, navigate to https://connect.microsoft.com/availableconnections.aspx, scroll down to the very bottom of the page and hit "Apply" next to Visual Studio connection.

Lol, you make it sound simple.... lol. Thank you again Einar. I've submitted the report as suggested.





Re: Visual C++ Language Internal compiler error

einaros

badone wrote:

Lol, you make it sound simple.... lol. Thank you again Einar. I've submitted the report as suggested.

I had to check myself, and felt equally stupid when I circled that page twice before spotting the section at the bottom Smile

That's perhaps something to note on in the "suggestions" part of the connect site Wink






Re: Visual C++ Language Internal compiler error

RobHaynes

I have experienced a very similar problem. I cannot un-install the 2.0 patch, since there doesn't seem to be an uninstall for it.

The kicker for me is that I'm dead in the water until this gets fixed. Line 9 of this gives me the error:

#include "stdafx.h"

using namespace System::Net;

using namespace System::Net:Tongue Tiedockets;

int main(array<System:Tongue Tiedtring ^> ^args)

{

Socket^ s;

s = gcnew Socket(AddressFamily::InterNetwork, SocketType:Tongue Tiedtream, ProtocolType::Tcp);

return 0;

}





Re: Visual C++ Language Internal compiler error

badone

As it turned out mine was actually corruption or incompatability in the build files. A complete clean (which I was hesitant to do due to customization issues) and rebuild fixed the problem. Apologies to anyone i confused :-)

Rob: That code compiles fine for me.

Cheers,

bad