Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. The Lounge
  3. Future C# features

Future C# features

Scheduled Pinned Locked Moved The Lounge
csharpvisual-studiobeta-testingquestionannouncement
50 Posts 25 Posters 9 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • W Wesner Moise

    I am contracting at MS right now, and have contacts with the W------ people. I don't know if I am aloud to mention codenames, despite the fact that Microsoft made the name public, everyone knows the name of the product, and we have an article on it. I mentioned the W------ code name before, which was already publicized in the Microsoft roadmap, but then I was reminded of my NDA agreement; so I deleted the article. What sort of future C# features would you like to see in VS 2004 (or 2005, etc as the case may be)? Can't mention ship dates-- so I am being general, it's a future version of VS, and VS (2003 is already taken). I know the C# developer guys and the feature set is still fluid--uh I mean MORE fluid than usual. If I specify the absolute level of fluidity, I might give away trade secrets. Give me some of your ideas and I will relay them to the C# developers. I am on a company mailing list in which they are asking for feedback, comments and wishlists. Thanks, Wes

    J Offline
    J Offline
    John Fisher
    wrote on last edited by
    #34

    I like several of the features already suggested, but I will be really, really, really disappointed if the next version of C# doesn't have Edit-and-Continue, when we've already been informed that VB.NET will have it....:| John
    "We want to be alone when we hear too many words and we feel alone when it has been a while since anyone has spoken to us." Paul David Tripp -- War of Words

    1 Reply Last reply
    0
    • W Wesner Moise

      I am contracting at MS right now, and have contacts with the W------ people. I don't know if I am aloud to mention codenames, despite the fact that Microsoft made the name public, everyone knows the name of the product, and we have an article on it. I mentioned the W------ code name before, which was already publicized in the Microsoft roadmap, but then I was reminded of my NDA agreement; so I deleted the article. What sort of future C# features would you like to see in VS 2004 (or 2005, etc as the case may be)? Can't mention ship dates-- so I am being general, it's a future version of VS, and VS (2003 is already taken). I know the C# developer guys and the feature set is still fluid--uh I mean MORE fluid than usual. If I specify the absolute level of fluidity, I might give away trade secrets. Give me some of your ideas and I will relay them to the C# developers. I am on a company mailing list in which they are asking for feedback, comments and wishlists. Thanks, Wes

      L Offline
      L Offline
      Leprosy
      wrote on last edited by
      #35

      OH HI, I WOULD LIKE A MAKE MY WEB APPLICATION SECURE BUTTON. I CANT FIND IT IN VS 2003. WHERE IS IT GONE TO? THANKS- CAPSLOXROX PS MAKE BUTTON LOOK LIKE THIS - :suss:

      1 Reply Last reply
      0
      • W Wesner Moise

        I am contracting at MS right now, and have contacts with the W------ people. I don't know if I am aloud to mention codenames, despite the fact that Microsoft made the name public, everyone knows the name of the product, and we have an article on it. I mentioned the W------ code name before, which was already publicized in the Microsoft roadmap, but then I was reminded of my NDA agreement; so I deleted the article. What sort of future C# features would you like to see in VS 2004 (or 2005, etc as the case may be)? Can't mention ship dates-- so I am being general, it's a future version of VS, and VS (2003 is already taken). I know the C# developer guys and the feature set is still fluid--uh I mean MORE fluid than usual. If I specify the absolute level of fluidity, I might give away trade secrets. Give me some of your ideas and I will relay them to the C# developers. I am on a company mailing list in which they are asking for feedback, comments and wishlists. Thanks, Wes

        J Offline
        J Offline
        jeff_martin
        wrote on last edited by
        #36

        Others have mentioned the one thing I want. Default parameters!

        1 Reply Last reply
        0
        • W Wesner Moise

          I am contracting at MS right now, and have contacts with the W------ people. I don't know if I am aloud to mention codenames, despite the fact that Microsoft made the name public, everyone knows the name of the product, and we have an article on it. I mentioned the W------ code name before, which was already publicized in the Microsoft roadmap, but then I was reminded of my NDA agreement; so I deleted the article. What sort of future C# features would you like to see in VS 2004 (or 2005, etc as the case may be)? Can't mention ship dates-- so I am being general, it's a future version of VS, and VS (2003 is already taken). I know the C# developer guys and the feature set is still fluid--uh I mean MORE fluid than usual. If I specify the absolute level of fluidity, I might give away trade secrets. Give me some of your ideas and I will relay them to the C# developers. I am on a company mailing list in which they are asking for feedback, comments and wishlists. Thanks, Wes

          K Offline
          K Offline
          Kastro
          wrote on last edited by
          #37

          Somehow providing delegate inheritance. Don't know how it could be done, but I'd like to be able to do something like the following...

          class MadeHappyEventArgs : EventArgs {
          ...
          }

          public delegate void MadeHappyEventHandler : EventHandler (Object sender, MadeHappyEventArgs e);

          class MakeHappyControl : Control {

          private static readonly Object MadeHappyEvent = new Object();
          
          public event MadeHappyEventHandler MadeHappy {
              add { Events.AddHandler(MadeHappyEvent, value); }
              remove { Events.RemoveHandler(MadeHappyEvent, value); }
          }
          
          protected void OnMadeHappy() {
              RaiseEvent(MadeHappyEvent, new MadeHappyArgs());
          }
          
          private void RaiseEvent(Object event, EventArgs args) {
              // The next line is what it would allow
              EventHandler handler = (EventHandler)Events\[event\];
              if (handler != null)
                  handler(this, args);
          }
          

          }

          Would be nice... It's a lot cleaner when you don't have to rewrite that RaiseEvent method for every type of EventArgs event.

          1 Reply Last reply
          0
          • W Wesner Moise

            I am contracting at MS right now, and have contacts with the W------ people. I don't know if I am aloud to mention codenames, despite the fact that Microsoft made the name public, everyone knows the name of the product, and we have an article on it. I mentioned the W------ code name before, which was already publicized in the Microsoft roadmap, but then I was reminded of my NDA agreement; so I deleted the article. What sort of future C# features would you like to see in VS 2004 (or 2005, etc as the case may be)? Can't mention ship dates-- so I am being general, it's a future version of VS, and VS (2003 is already taken). I know the C# developer guys and the feature set is still fluid--uh I mean MORE fluid than usual. If I specify the absolute level of fluidity, I might give away trade secrets. Give me some of your ideas and I will relay them to the C# developers. I am on a company mailing list in which they are asking for feedback, comments and wishlists. Thanks, Wes

            A Offline
            A Offline
            Adam Wimsatt
            wrote on last edited by
            #38

            I would just really like to see the Office Assitant integrated into the IDE. I just love that cute little clippy. Ok !really :rolleyes: X| [Edit] Someone beat me to it.. [/Edit] --Sig-- Adam Wimsatt www.liquidneon.com

            1 Reply Last reply
            0
            • I igor1960

              This can already be done using the command-line compiler - just not VS.NET's built-in compiler Could they refference each other?... "...Ability to type is not enough to become a Programmer. Unless you type in VB. But then again you have to type really fast..." Me

              D Offline
              D Offline
              David Stone
              wrote on last edited by
              #39

              VS.NET uses the csc and vbc compilers...just not to their full extent.


              I have also lived some years in Spain, and there people don't accept that you speak bad spanish. I usually compensate by speaking loud and accusing people of being stupid because they don't understand me. It usually works quite well. -jhaga on non-native languages

              1 Reply Last reply
              0
              • R Russell Morris

                igor1960 wrote: 1. Ability to compile mixed files written in any CLR languages in one assembly; This can already be done using the command-line compiler - just not VS.NET's built-in compiler -- Russell Morris "So, broccoli, mother says you're good for me... but I'm afraid I'm no good for you!" - Stewy

                C Offline
                C Offline
                Chris Richardson
                wrote on last edited by
                #40

                They are both the same compiler. I'm sure it's an IDE limitation. Chris Richardson

                1 Reply Last reply
                0
                • W Wesner Moise

                  I am contracting at MS right now, and have contacts with the W------ people. I don't know if I am aloud to mention codenames, despite the fact that Microsoft made the name public, everyone knows the name of the product, and we have an article on it. I mentioned the W------ code name before, which was already publicized in the Microsoft roadmap, but then I was reminded of my NDA agreement; so I deleted the article. What sort of future C# features would you like to see in VS 2004 (or 2005, etc as the case may be)? Can't mention ship dates-- so I am being general, it's a future version of VS, and VS (2003 is already taken). I know the C# developer guys and the feature set is still fluid--uh I mean MORE fluid than usual. If I specify the absolute level of fluidity, I might give away trade secrets. Give me some of your ideas and I will relay them to the C# developers. I am on a company mailing list in which they are asking for feedback, comments and wishlists. Thanks, Wes

                  A Offline
                  A Offline
                  Alvaro Mendez
                  wrote on last edited by
                  #41

                  C# - Default parameters - More powerful operator overloading - Java's inner classes -- these are non-static nested classes that can only be instanciated from an instance of their outer class. Inner classes have full access to their outer class's members via a hidden reference to the outer class instance (OuterClass.this). - As an alternative to multiple implementation inheritance, it would be nice to tell the class that an interface is implemented in some member class. For example:

                  class MyClass : IMyInterface
                  {
                  ClassThatAlreadyImplementsMyInterface m_c = new ClassThatAlreadyImplementsMyInterface();

                  MyClass()
                  {
                  m_c.implements(IMyInterface);
                  }
                  }

                  The implements keyword (or something like it) would a pseudo-directive that would tell the compiler to automatically generate the IMyInterface's methods inside of MyClass and just have them call m_c's methods directly. This would be a way to simulate implementation inheritance using containment. .NET - The entire Win32 API should be ported to .NET. I don't see why something as basic as MessageBeep has to be imported. Thanks, Alvaro


                  If you want to get to the top, prepare to kiss a lot of bottom. -- despair.com

                  1 Reply Last reply
                  0
                  • W Wesner Moise

                    I am contracting at MS right now, and have contacts with the W------ people. I don't know if I am aloud to mention codenames, despite the fact that Microsoft made the name public, everyone knows the name of the product, and we have an article on it. I mentioned the W------ code name before, which was already publicized in the Microsoft roadmap, but then I was reminded of my NDA agreement; so I deleted the article. What sort of future C# features would you like to see in VS 2004 (or 2005, etc as the case may be)? Can't mention ship dates-- so I am being general, it's a future version of VS, and VS (2003 is already taken). I know the C# developer guys and the feature set is still fluid--uh I mean MORE fluid than usual. If I specify the absolute level of fluidity, I might give away trade secrets. Give me some of your ideas and I will relay them to the C# developers. I am on a company mailing list in which they are asking for feedback, comments and wishlists. Thanks, Wes

                    W Offline
                    W Offline
                    Wesner Moise
                    wrote on last edited by
                    #42

                    For some reason, Clippy the Office Assistant, is something that a lot of you guys want, unless you are joking... Rest assured, I will push hard on getting Clippy included. :) Thanks, Wes

                    1 Reply Last reply
                    0
                    • N Nemanja Trifunovic

                      Wesner Moise wrote: What sort of future C# features would you like to see in VS 2004 (or 2005, etc as the case may be)? 1. Make the GC optional and give us proper destructors. 2. const parameters and const methods. 3. Multiple inheritance. 4. Default parameters. 5. Non-member functions.

                      W Offline
                      W Offline
                      Wesner Moise
                      wrote on last edited by
                      #43

                      Managed C++ is being improved too... and will probably be competitive with C# at some point. Seems like you really want an improved MC++. Thanks, Wes

                      N J 2 Replies Last reply
                      0
                      • W Wesner Moise

                        I am contracting at MS right now, and have contacts with the W------ people. I don't know if I am aloud to mention codenames, despite the fact that Microsoft made the name public, everyone knows the name of the product, and we have an article on it. I mentioned the W------ code name before, which was already publicized in the Microsoft roadmap, but then I was reminded of my NDA agreement; so I deleted the article. What sort of future C# features would you like to see in VS 2004 (or 2005, etc as the case may be)? Can't mention ship dates-- so I am being general, it's a future version of VS, and VS (2003 is already taken). I know the C# developer guys and the feature set is still fluid--uh I mean MORE fluid than usual. If I specify the absolute level of fluidity, I might give away trade secrets. Give me some of your ideas and I will relay them to the C# developers. I am on a company mailing list in which they are asking for feedback, comments and wishlists. Thanks, Wes

                        J Offline
                        J Offline
                        JWood
                        wrote on last edited by
                        #44

                        C# is a bad version of java. Why bother? If you can compile it - REALLY compile it I would say that would be a good feature. PCODE type of crap is really bogus and fools no one least of all the people buying the stuff.

                        J 1 Reply Last reply
                        0
                        • W Wesner Moise

                          Managed C++ is being improved too... and will probably be competitive with C# at some point. Seems like you really want an improved MC++. Thanks, Wes

                          N Offline
                          N Offline
                          Nemanja Trifunovic
                          wrote on last edited by
                          #45

                          Wesner Moise wrote: Seems like you really want an improved MC++. Yes!!! :jig:

                          1 Reply Last reply
                          0
                          • J JWood

                            C# is a bad version of java. Why bother? If you can compile it - REALLY compile it I would say that would be a good feature. PCODE type of crap is really bogus and fools no one least of all the people buying the stuff.

                            J Offline
                            J Offline
                            J Dunlap
                            wrote on last edited by
                            #46

                            I wish they would include a native compiler that would compile .NET assemblies into native code. There exists a compiler like this, but MS should make one themselves, and distribute it with VS.NET.

                            "Blessed are the peacemakers, for they shall be called sons of God." - Jesus
                            "You must be the change you wish to see in the world." - Mahatma Gandhi

                            1 Reply Last reply
                            0
                            • W Wesner Moise

                              Managed C++ is being improved too... and will probably be competitive with C# at some point. Seems like you really want an improved MC++. Thanks, Wes

                              J Offline
                              J Offline
                              J Dunlap
                              wrote on last edited by
                              #47

                              Well, for me, I would like to see those features in C#. I really like the clean syntax of C# (I don't like having to declare properties as _property, etc, and all the things MC++ has to do for compatibility with unmanaged C++). I think the things he listed could be added to C#, and I would really like it if they would be.

                              "Blessed are the peacemakers, for they shall be called sons of God." - Jesus
                              "You must be the change you wish to see in the world." - Mahatma Gandhi

                              1 Reply Last reply
                              0
                              • W Wesner Moise

                                I am contracting at MS right now, and have contacts with the W------ people. I don't know if I am aloud to mention codenames, despite the fact that Microsoft made the name public, everyone knows the name of the product, and we have an article on it. I mentioned the W------ code name before, which was already publicized in the Microsoft roadmap, but then I was reminded of my NDA agreement; so I deleted the article. What sort of future C# features would you like to see in VS 2004 (or 2005, etc as the case may be)? Can't mention ship dates-- so I am being general, it's a future version of VS, and VS (2003 is already taken). I know the C# developer guys and the feature set is still fluid--uh I mean MORE fluid than usual. If I specify the absolute level of fluidity, I might give away trade secrets. Give me some of your ideas and I will relay them to the C# developers. I am on a company mailing list in which they are asking for feedback, comments and wishlists. Thanks, Wes

                                J Offline
                                J Offline
                                Joe Woodbury
                                wrote on last edited by
                                #48

                                1. Deterministic destructors. GC is terrible for cleaning up resources. I actually had a great idea for this: a scoped keyword. This keyword could be used in the class declaration, in which case it would always have the destructor called upon exiting scope OR it could be used when instantiating a class. 2. A built in resource editor. 3. The addition of a C++ like include statement. 4. Allow strings to be delared on multiple lines without the "+" sign. This is probably the dumbest thing in C#. 5. Default arguments. This could be accomplished by having the compiler simply create a version with all the arguments that have the ones with reduced arguments jump to the first internally with the argument filled in. 6. Templates. C# is strongly typed in some areas, but not others. The collection classes allow for horrendous mistakes. 7.... Ah, bag it, I'll just keep using C++/MFC.

                                1 Reply Last reply
                                0
                                • D David Stone

                                  Totally agree with you on everything but 3d, I don't really need UML models in my code or whatnot. DB diagrams might be nice. But what I'd really love is a CodeDOM parser. That would be awesome. leppie has pointed out to me that the Microsoft.VisualStudio.dll Assembly has a CodeDOM parser in it, but that it kinda sucks for handwritten code, and works marginally well with designer generated code...but that's kinda worthless now, isn't it...


                                  I have also lived some years in Spain, and there people don't accept that you speak bad spanish. I usually compensate by speaking loud and accusing people of being stupid because they don't understand me. It usually works quite well. -jhaga on non-native languages

                                  D Offline
                                  D Offline
                                  Daniel Turini
                                  wrote on last edited by
                                  #49

                                  David Stone wrote: That would be awesome. leppie has pointed out to me that the Microsoft.VisualStudio.dll Assembly has a CodeDOM parser in it, Great. Now you ruined a perfect night of sleep. :)

                                  // Quantum sort algorithm implementation
                                  while (!sorted)
                                  ;

                                  1 Reply Last reply
                                  0
                                  • W Wesner Moise

                                    I am contracting at MS right now, and have contacts with the W------ people. I don't know if I am aloud to mention codenames, despite the fact that Microsoft made the name public, everyone knows the name of the product, and we have an article on it. I mentioned the W------ code name before, which was already publicized in the Microsoft roadmap, but then I was reminded of my NDA agreement; so I deleted the article. What sort of future C# features would you like to see in VS 2004 (or 2005, etc as the case may be)? Can't mention ship dates-- so I am being general, it's a future version of VS, and VS (2003 is already taken). I know the C# developer guys and the feature set is still fluid--uh I mean MORE fluid than usual. If I specify the absolute level of fluidity, I might give away trade secrets. Give me some of your ideas and I will relay them to the C# developers. I am on a company mailing list in which they are asking for feedback, comments and wishlists. Thanks, Wes

                                    J Offline
                                    J Offline
                                    Joey Bloggs
                                    wrote on last edited by
                                    #50

                                    Just shitcan the whole sorry mess and rewrite the BCL as open source C++ libraries. :|

                                    1 Reply Last reply
                                    0
                                    Reply
                                    • Reply as topic
                                    Log in to reply
                                    • Oldest to Newest
                                    • Newest to Oldest
                                    • Most Votes


                                    • Login

                                    • Don't have an account? Register

                                    • Login or register to search.
                                    • First post
                                      Last post
                                    0
                                    • Categories
                                    • Recent
                                    • Tags
                                    • Popular
                                    • World
                                    • Users
                                    • Groups