Search

You searched for the word(s): userid:115757

Matching Posts

  • Re: What is the main difference between C# and C++?

    I'm not quite sure what you mean by "generic programming" but to avoid confusion, C# 2.0 does have "generics" which allow you to create type-safe collections, e.g., Stack<T> As for MI, I the 10 years or so I programmed in C++, I never once used MI except to teach how it works. Interfaces provide much (tough not quite all) of the functionality,
    Posted to C# (Forum) by jliberty on 5/29/2005
  • Re: What is the main difference between C# and C++?

    Let's see. First, I oversimplified and said that C++ does not have pointers. Of course it does, I write about it in chapter 22 of my book Programming C# (O'Reilly). But in c# pointers are rarely used except to interoperate (usually with COM) and they are ugly and to be avoided when possible. Second, To respond to Feran3rd who said "You only get memory leaks if you don't know what you're doing or you slip up" -- to that I reply that "slippinng up" is (almost) inevitable. C++ litters the ground with
    Posted to C# (Forum) by jliberty on 5/26/2005
  • Re: What is the main difference between C# and C++?

    First, C++ is designed to run on any platform, while C# runs on .NET. Second, C# has garbage collection and a host of other features, and does not have pointers (though it does have references). C++ has multiple inheritance, C# does not, but it does have interfaces. In C# properties are first class members of the language. In C# delegates (essentially pointers to member functions) are also first class members of the language, and are type safe. There are quite a few more. You may be interested in
    Posted to C# (Forum) by jliberty on 5/24/2005
  • Re: Password Regular Expression

    By default, passwords must be "strong" which means: 1. At least 8 characters 2. At least one uppercase and one lowercase letter 3. At least one non-alphabetic character Good luck!
    Posted to Personal Site Starter Kit (Forum) by jliberty on 5/24/2005
  • Moving to C# 2.0

    [This is a one time announcement that I hope will be of interest to this group] I'm pleased and proud to announce that I have two new books on C# 2.0 now available from O'Reilly Media. The first, Visual C#: A Developer's Notebook is designed for experienced C# 1.x programmers who want to move quickly to C# 2.0. This book shows you what is new in the language, in Visual Studio and in building both Windows and Web applications. It also shows what is new in data access. The second is Programming C#
    Posted to Announcements (Forum) by jliberty on 5/15/2005
  • Re: Properties in master pages

    You are terrific; that did it, thanks!
  • Re: Master pages and getting the SiteMap.CurentNode

    The problem is that I'm brain-dead. I was trying to access it through the Master page. It works fine and I'm sorry to have wasted your time.
  • Master pages and getting the SiteMap.CurentNode

    In one part of the documentation it is stated that there is great advantage to putting the SiteeMapDataSource and the TreeView into the master page (makes sense to me) However, from what I can see, if you do so, there is no way for the content page to access the SiteMap object and its CurrentNode property. Is that a bug or a design flaw or am I doing something wrong? Thanks. jliberty@libertyassociates.com
  • Properties in master pages

    In previous CTP's it was possible to declare a public property in a master page, and then access that property using Master.<propertyname> from the content page. IN fact, the documentation of MasterPage Class says: All public properties in the master page class are available to the content page's base class through the Master property, using the notation Master . PropertyName . This no longer seems to work. Is this a bug, or am I doing something wrong? Thanks. jliberty@libertyassocaites.com
Page 1 of 1 (9 items)