ASP.NET application freezes when COM object is instantiated

[Ralf Müller]

In a WindowsForms application it works just fine. Why not in ASP.NET?

The interop assembly used was in both cases auto-generated by Visual Studio
..NET from the same .dll

The code is exactly the same in WindowsForms and WebForms:

private void button1_Click(object sender, System.EventArgs e) {
ImyCOMObject obj = new myCOMObjectClass(); // ASP.NET freezes here -
WindowsForm works perfectly
ISearchResult res = obj.Search(tbSearch.Text);
int count = res.Count;
for(int i = 0; i < res.Count; i++) {
....
}
}

 

[Scott Allen]

Do you know if the COM component uses the STA threading model? If so, you'll
need aspcompt="true" in your @ Page directive to set a compatible apartment
model for the thread executing the aspx page.

HTH,

 

[Saravana]

You need to set aspcompat=true. For more details about aspcompat, check out
this article
http://www.aspnetfaq.com/default.aspx?CategoryId=48&FaqId=139&SearchString=

 

[Ralf Müller]

Thank you, Saravana and Scott! It works... somehow. And it works even better
since I've found out how to destroy my COM-Object again.
But I've got one weird problem left: The interface "IAdresse" in the interop
library offers a property called "AnsprechpartnerCount" which is of type
int. This property works fine in the WindowsForms application but gives me a
COMException when using it in my WebApplication. Are there any other
differences between COM handling in ASP.NET and Windows Forms I should know
about?

Greetings, Ralf