Forgot your password?
Sign in with
Article Help Forum
Submit an article or tip
Import GitHub Project
Import your Blog
Ask a Question
View Unanswered Questions
View All Questions
View C# questions
View C++ questions
View PHP questions
View Python questions
All Message Boards...
Running a Business
Sales / Marketing
Collaboration / Beta Testing
Design and Architecture
Internet of Things
C / C++ / MFC
ATL / WTL / STL
Objective-C and Swift
Hardware & Devices
Hosting and Servers
.NET (Core and Framework)
Site Bugs / Suggestions
Spam and Abuse Watch
The Insider Newsletter
The Daily Build Newsletter
Most Valuable Professionals
The CodeProject Blog
Where I Am: Member Photos
The Insider News
The Weird & The Wonderful
What is 'CodeProject'?
Ask a Question
Bugs and Suggestions
Article Help Forum
Comments by gwithey (Top 14 by date)
The following using the solution you linked has reduced my sort time 2 fold and enabled me to cancel with a token...
// Sort by Ascending
m_listViewItems = new ObservableCollection<renishawlistitem>(
.WithDegreeOfParallelism(2) // Sorts 2 in parellel (Down from 6 seconds to 3 over 1.5 million)
.WithCancellation(m_cancelationTokenSource.Token) // Enables the sort to quit when token is false on dispose etc
x => (primaryTypeIsKnown)
? Convert.ChangeType(x.SubItems[sortIndex], primaryItemType,
x => (secondaryTypeIsKnown)
? Convert.ChangeType(x.SubItems[columnToCompareIndex], secondaryItemType,
Thank you F.Xaver i will give this a try
Thanks for the help with this, it allows me to at least determine which ones are obsolete and indicate this within the UI.
I still don't know if these could be linked to and display a property grid that relates to a control instance opposed to its type. However will see what i can do.
I wish to display them for regression testing of these properties to display any that are currently deprecated or non brawsable within a property grid.
Thanks for this, i have looked though the documentation and it is a useful resource for showing the currently deprecated properties dlls etc in .Net.
I have been trying to query the obsolete attribute using reflection but have not yet discovered a method of doing so and could not see anything which may lead me to this within the resource =s.
I suppose my original goal may seem odd but ideally i want to display depreciated,normal and non browsable properties in separate property grids. This is to allow testing of all attributes.
This was exactly what i was looking for and worked perfectly, thanks Alan =)
Ok thanks this could provide a possible solution, we already have a similar tool 'XenoCode' so could take this train of thought. I am just researching the issue at this stage before it is decided which route may be deemed the optimum direction for the project.
Ok this makes sense, i suppose if i require security the exception route may be a good idea or something similar at least as not sure if the user of the dll's may be able to bury the exception. Thanks for the advice
Ah i thought this may be the case, i have read the documentation and tried to think of a solution however thought maybe somebody had stumbled across a way of achieving this even if it is a little far fetched. So a group of dlls are not able to share the class among themselves but not the code using them when distributed.
Thank you, this worked great. The tool-strip now appears blended into the background.
Reason for my vote of 5
Automatic vote of 5 for accepting answer.
This is what i thought, i was hoping there may be a way but these solutions will work so will give probably end up using the form method if that is possible using CAB.
Thanks for the Answer.
I tried to remove the file from source control it is there but says not downloaded and when i right click delete is greyed out. Do you know how i can resolve this.
I get it, i didnt understand how everything worked since the site changed, i think you are right just dont know how to fix it, the problem only occurs in one project of my solution. I can add the class to any other
Last Updated 1 Jan 1900
All Rights Reserved.