Post reply

Warning: this topic has not been posted in for at least 120 days.
Unless you're sure you want to reply, please consider starting a new topic.
Name:
Email:
Subject:
Message icon:
Verification:
Type the letters shown in the picture
Listen to the letters / Request another image

Type the letters shown in the picture:
What is the last letter in the word "SlickEdit":
How many LETTERS are in the following? "a1b2c3":
Which number is missing?  "12345689":

shortcuts: hit alt+s to submit/post or alt+p to preview


Topic Summary

Posted by: Wanderer
« on: July 02, 2009, 03:12:03 AM »

-- Better C#/WPF support. 
    -- Working in a file with a .cs extension is almost unusably slow. 
    -- SlickEdit doesn't deal with the whole .xaml/.xaml.cs situation very well.  (Objects declared in the xaml aren't tagged, and you can't find them by trying look them up or looking for references.)
        I am switching more and more to VisStudio when working on C#/WPF stuff.

-- Better ATL/COM (C++) support.  Tagging is terrible for many ATL constructs.
Completion is non-existent for constructs like CComPtr:
   CComPtr<EnvDTE::Windows> pWindows;
pWindows->                  // SlickEdit offers nothing...
    Same here: using VisStudio more and more just to get IntelliSense.