Coffeehouse Thread

10 posts

Forum Read Only

This forum has been made read only by the site admins. No new threads or comments can be added.

when are we going to see how things are for Orcas?

Back to Forum: Coffeehouse
  • User profile image
    Shark_M

    Hi guys,
       I just wanted to know if C9 is going to give us some view as to how things are going for Visual Studio Orcas and .Net framework 3.0? How is the C# team and vb.net team comming along? what is the new cool stuff they are doing?

    Its been awhile since C9 gave us a view of what is happening there. So when is it going to happen? any time soon?Smiley

  • User profile image
    yag

    We just released a new tech preview for Linq (due to ship in C# 3.0 and VB9).

    http://msdn.microsoft.com/netframework/future

    yag

  • User profile image
    Cybermagell​an

    yag wrote:
    We just released a new tech preview for Linq (due to ship in C# 3.0 and VB9).

    http://msdn.microsoft.com/netframework/future

    yag


    Please stay, don't leave...we like softies around here Smiley

  • User profile image
    staceyw

    yag wrote:
    We just released a new tech preview for Linq (due to ship in C# 3.0 and VB9).

    http://msdn.microsoft.com/netframework/future

    yag


    Man... You miss 1 day on the Linq forum and look what happens.  Cheers.

  • User profile image
    spoofnozzle

    I know that it sounds like an anomoly in an OOP language... but I would really like to see an 'include' directive, which can pull code in from a .h file, and be able to provide reference to it in the IDE.

    There are plenty of places where using an object is not a suitable way to re-use code, and an 'include' directive is more applicable.

    eg. -- Using directives... you can't 'objectify' these, and so need to type them into every class that needs them.

    Far easier would be to use a header file to store these as re-usable elements... something along these lines perhaps... ??

    MyHeaders.h
    ================================
    include UsingCommon
    {
       using System;
       using System.Collections;
       using System.ComponentModel;
       using System.Configuration;
    }

    include UsingData
    {
       using System.Data;
       using System.Data.Common;
    }

    include UsingText
    {
       using System.Text;
       using System.Text.RegularExpressions;
    }

    include UsingWeb
    {
       using System.Web;
       using System.Web.Security;
       using System.Web.Services;
       using System.Web.SessionState;
       using System.Web.UI;
       using System.Web.UI.HtmlControls;
       using System.Web.UI.WebControls;
       using System.Web.UI.WebControls.WebParts;
    }

    include UsingXml
    {
       using System.Xml;
       using System.Xml.XPath;
       using System.Xml.Xsl;
    }


    MyClass.cs
    =====================================
    include UsingCommon;
    include UsingWeb;

  • User profile image
    staceyw

    spoofnozzle wrote:
    

    I know that it sounds like an anomoly in an OOP language... but I would really like to see an 'include' directive, which can pull code in from a .h file, and be able to provide reference to it in the IDE.

    There are plenty of places where using an object is not a suitable way to re-use code, and an 'include' directive is more applicable.

    eg. -- Using directives... you can't 'objectify' these, and so need to type them into every class that needs them.

    Far easier would be to use a header file to store these as re-usable elements... something along these lines perhaps... ??

    MyHeaders.h
    ================================
    include UsingCommon
    {
       using System;
       using System.Collections;
       using System.ComponentModel;
       using System.Configuration;
    }

    include UsingData
    {
       using System.Data;
       using System.Data.Common;
    }

    include UsingText
    {
       using System.Text;
       using System.Text.RegularExpressions;
    }

    include UsingWeb
    {
       using System.Web;
       using System.Web.Security;
       using System.Web.Services;
       using System.Web.SessionState;
       using System.Web.UI;
       using System.Web.UI.HtmlControls;
       using System.Web.UI.WebControls;
       using System.Web.UI.WebControls.WebParts;
    }

    include UsingXml
    {
       using System.Xml;
       using System.Xml.XPath;
       using System.Xml.Xsl;
    }


    MyClass.cs
    =====================================
    include UsingCommon;
    include UsingWeb;



    Not sure I am sold on that yet.  That will tend to be "using" more namespaces then you actually need.   Not sure.

  • User profile image
    ScanIAm

    Yeah, what would be the point in doing that?  The compiler will pretty quickly tell you what is missing.

  • User profile image
    spoofnozzle

    Start putting together a large project with hundreds of classes... and you'll soon see why an include directive would be handy.

  • User profile image
    staceyw

    spoofnozzle wrote:
    Start putting together a large project with hundreds of classes... and you'll soon see why an include directive would be handy.


    Have worked with ~100 and never found that an issue.  If you really need that sort of thing, you can define snippets.  I never really cared for rats nest of *.h files in windows.  Different strokes.

  • User profile image
    spoofnozzle

    staceyw wrote:
    If you really need that sort of thing, you can define snippets.


    ...and then you find you need to make a change.

    You can change the header file, or you go find/edit every instance.

Conversation locked

This conversation has been locked by the site admins. No new comments can be made.