| |
 |
Saturday, April 06, 2002 |
Ingo reports: I'm on http://www.go-mono.net! Advanced .NET Remoting from Ingo Rammer is now available. Ingo helped us to implement the proxy support and the book is a valuable resource for anyone interested in remoting.
You're welcome and thanks for the link!
[Ingo Rammer's DotNetCentric]
Its clear, from his knowledge (and the chat yesterday), that this will be the definitive book on .NET Remoting. Now, if I could just get him to answer my Rotor problem -)
8:37:43 AM 
|
|
Ingo posts: .NET Remoting chat - reprise.
Today morning (from 1:00 a.m to 2:00 a.m CET) Microsoft hosted a .NET Remoting chat.
The development team answered questions from users and told us about the features which are planned for future releases. The official chat transcript isn't online yet, so I quote from what I remember:
- Microsoft will release a sample application which provides authenticated Remoting for objects hosted outside IIS. In my opinion, this has been the missing feature #1 and some others in the chat agreed with this. Tomas and I therefore will focus on a different area and not implement the SSPI channel. Mike Woodring (who's been working on such a channel independently from us) also announced to stop the development of his channel.
- Microsoft will look into improving the performance of the HTTPChannel when hosted in IIS.
- The context implementation might be changed. This means that ContextBoundObject and things like context properties, context attributes and the interfaces like IContributeObjectSink, which aren't yet documented might be different in the next version.
This is not an official statement, it's just what I remember from the chat.
By the way, has anyone saved a log of this chat? If yes, could you please send it to me by email (rammer@sycom.at)? Thanks a lot! [Ingo Rammer's DotNetCentric]
8:25:04 AM
|
|
I met our "famous" Ingo Rammer [Ingo Rammer's DotNetCentric] yesterday. Well, virtually that is -) He was particpating in a .NET Remoting chat on MSDN with the .NET Remoting team. The scary thing was thet he was answering most of the questions. He seems to know more about Remoting than the team that wrote it -)
8:23:54 AM
|
|
Another 2 days of banging my head aggainst the wall with mixing managed C# components together with ATL COM native components. As I said earlier, in part one, I have been working on trying to give myself and my team a productivity boost. I have been working on a full blown tool development environment fully integrated with Microsoft Visual C++.NET. As I said earlier, VSIP is extremely difficult to grok and work with. So I have been persuing a strategy of mixing VSIP with pieces of the VS.NET automation model to do some things like adding tools to the toolbox, menus, adding custom code, etc easier.
The big thing I ran into the last two days and got stuck on, is that I was not able to step into the managed C# assembly from the native ATL/C++ COM component in the debugger. I have the assembly in the GAC so I thought it was some weird issue. The .NET mailing list was unhelpful. I finally found the solution yesterday.
I guess I can't paste in an image here but the answer lies in Project - Configuration Properties - Debugging - Debuggers, which is usually set to Auto. I changed this to "Mixed" and it worked. It seems that Auto will do managd or unmanaged debugging but not both. Mixed combines both.
8:19:45 AM
|
|
© Copyright 2002 Sam Gentile.
|
|
|
|
|
