http://msdn2.microsoft.com/en-us/library/ms404463.aspx details ICeeFileGen as
being deprecated; but, CreateICeeFileGen
(http://msdn2.microsoft.com/en-us/lib...59(d=ide).aspx) has not.

If ICeeFileGen is deprecated, what is the suggested alternative to
CreateICeeFileGen, or what is the suggested alternative to ICeeFileGen in
general?

--
http://www.peterRitchie.com/

Hi PRSoCo,

Thanks for your post!

I think this is a MSDN document issue, which forgets to mark
CreateICeeFileGen as deprecated. Regarding the suggested alternative for
ICeeFileGen, I still did not find a public one. I will give it an internal
consulting on this. I will update you ASAP. Thanks.

Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Thanks Jeffery, looking forward to your follow-up.

Thanks
--
http://www.peterRitchie.com/


""Jeffrey Tan[MSFT]"" wrote:

Hi PRSoCo,

Thanks for your patient. Yes, I have contacted our CLR team regarding this
issue. 2 developers seem to believe that this interface will not be
deprecated in the plan. And using it will not yield any warnings or
messages. Anyway, we are still contacting the ICeeFileGen owner currently.
I hope we can get the confirmation from him. I will update here ASAP.

Thanks.

Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Hi Jeffery, thanks for the update.

--
http://www.peterRitchie.com/


""Jeffrey Tan[MSFT]"" wrote:

Hi PRSoCo,

Thanks for your patient.

Yes, after discussing this with the CLR team, they confirmed that this
interface will be deprecated in .Net3.0, you can use it in .NET 2.0 without
any problems. Many compilers are using it (C#, VB, J#, ...), so it is not
going to disappear anytime soon. I assume in .Net3.0, there will be a
workaround for this interface.

Hope this helps.

Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.