PureComponents .NET Suite?

Discussion PureComponents .NET Suite?

  • Tuesday, June 29, 2010 9:06 AM
     
     

    I am looking into the PureComponents .NET Suite for a Winforms project. The controls seem to offer a lot of nice function but I am concerned about their stability. Does anyone have experience with these controls?

    http://www.purecomponents.com

    Regards,

    Steve

All Replies

  • Wednesday, June 30, 2010 3:08 PM
     
     

    Hi Steve,

    I would recommend the Nevron .NET Vision controls: http://www.nevron.com

     

    Regards,

    Victor

     

     

     

     

     

     

  • Thursday, March 10, 2011 3:12 PM
     
     
    I've bought .NET Winforms 2010.1 last week.

    It's a SWINDLE.
    Nobody answer by email.
    No phone number
    No postal address

    It's not installing well under Win 7x64 with Visual Studio 2010.

    Somebody called STEVE already 'work' in PureComponents company so this post is an ADVERTISEMENT.

    DON'T BUY THEIR PRODUCTS

    Vincent

  • Friday, March 25, 2011 3:31 PM
     
     
    Hmmmm, that's a shame.  I have been using PureComponents controls in my X86 Windows applications (some very complex) since 2008 and have not experienced a problem getting customer support.  Of course, I have not requested support for over a year but these controls in my opinion are very stable.
  • Monday, April 25, 2011 12:25 AM
     
     
    Hmmmm, that's a shame.  I have been using PureComponents controls in my X86 Windows applications (some very complex) since 2008 and have not experienced a problem getting customer support.  Of course, I have not requested support for over a year but these controls in my opinion are very stable.
    Same here.  I've even upgraded to the latest, and haven't had a problem with the components.  Again, I've not needed support, but I haven't had any problems either.
  • Wednesday, April 27, 2011 9:45 PM
     
     

    For those of you that are not having problems, would you mind discussing how

    you got the components to work??

     

    I am having a great difficulty in initializing the component and assigning
    values, I have never seen or had any other components that were so
    deeply subbed and required such an extensive line of code for one value.

     

    I just purchased, luckily very cheaply, and have no support response after
    3 e-mails.

     


  • Tuesday, July 12, 2011 1:17 AM
     
     

    <*Sigh*> I'm right there with you.  I fell for it too.  You get what you pay for.  The controls look great and work great in the demos, but I can't get past the licensing to even be able to create code to test in debug mode.  It does look like they have abandoned ship at this point.  Even the customer portal has been shut down and the web site is reduced to one page.

     

    On a good note, at least I can use their tools to learn from.  And I've learned a valuable lesson in purchasing software.

     

    If anyone knows how to get past the license issue for debugging, can you please let us know?


    Greg Kowieski The World On-Line
  • Tuesday, September 27, 2011 9:15 AM
     
     

    I purchased the Winforms Suite but after my laptop died and I lost the licence key I re-installed the software however after three months still can't get anyone to reply to my requests to re-supply the licence.

     

    PureComponents support sucks!

  • Tuesday, January 10, 2012 12:42 AM
     
     

    DO NOT BUY THIS PRODUCT - DO NOT BUY THIS PRODUCT - DO NOT BUY THIS PRODUCT

    I purchased it last year (with source code) and I only got to use it now and this is a complete con to get people to buy it for cheap and not only do they product not work, their support is practically non-existent. It's that bad that it's been removed from the likes of ComponentSource.com

    Since I had the code, I decided to give it a shot and remove the licensing element out of it, and after spending a couple of hours on it and getting one of their main libraries to compile and get a solution to compile, I'm still getting error that some files are not found when it should not be the case.

    I could technically try to do the other 2 remaining main components, but I have a feeling I'll be waisting my time!!!

    Seriously dissapointing ... As someone else above (or elsewhere said!)... I guess you get what you paid for!!! The sad part is when you look at the code, it's actually quite clean & documented, but still dissapoiting overall..

    We use much dearer product in our main product and while this was for a personal project, I can see why I'd recommend these products over this one any day!!!

    There are other products out there which are seriously reliable and I know as I've used them in the past and that are also "cheap" ($300) and while they still don't beat the $1500 from larger companies in regards to features, they still provided amazing features for the price.

    Don't know if I can advertise for them, so I won't post their name here, but look around and you'll find them!! JUST DON'T BUY FROM PureComponents.com!!!

    Still can't believe I'm still getting their "promotional" news letters considering the state of the product!! They are obviously trying to con as many people as possible and for as long as possible!!!

    T.

  • Saturday, January 14, 2012 8:36 PM
     
     

    Yes, the support of PurComponents sucks. I don't get any answer after 4 mails, but in the beginning it was very good. The answer comes after 12-24 hours. And the documentation are not so good and not so bad.

    I'm using the PureComponents since about 3 years and they are stabil.

    And I'm using the 60 Free Controls from DevExpress.

    https://www.devexpress.com/Products/Free/NetOffer/

     


    • Edited by Mike Berger Saturday, January 14, 2012 8:39 PM
    •  
  • Wednesday, February 08, 2012 6:06 AM
     
      Has Code

    We use:

    PureComponents.ActionSet.Licensing.RunTimeLicenseKey = "XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX";

    PureComponents.EntrySet.Licensing.RunTimeLicenseKey = "XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX";

    PureComponents.ScheduleSet.Licensing.RunTimeLicenseKey = "XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX";

    in our program.cs[Main] before anything else.  I did notice that we are using the 2009 version.  I personally like the suite.  I don't think anyone has anything to complain about spending $19.00 for a site license.

  • Tuesday, March 06, 2012 11:57 PM
     
      Has Code

    I've been using PureComponents since 2008.  Support used to be good but now, like others have mentioned, zero response to emails.  Before trying to contact them I went ahead and bought 2010 for $19 then it sat there for a year and here I am now trying to use it to upgrade an existing application.  So NO, using something else is not an option.

    However, now that I'm using VS 2010 these dumb components will not license at all!

    It was never an issue before:

    Public Sub New() PureComponents.EntrySet.Licensing.RunTimeLicenseKey = "xxxx-xxxx-xxxx........." ' This call is required by the designer. InitializeComponent() ' Add any initialization after the InitializeComponent() call. End Sub

    This just does not work at all.  That dang trial popup comes up on the production machines.  Dev machine is fine.

    Everyone gets the source with purchase.  Has anyone looked to see if all this nonsense can be diverted?


  • Wednesday, March 07, 2012 7:52 AM
     
     

    Hello JEmlay,

    I had the same when I was changed to VS2010. Then I deleted the license file. After publish a new version the Trial Popup was gone.

    Mike

  • Monday, March 19, 2012 2:53 AM
     
     

    I have Visual Studio 2010 64 bit also.  I did buy this and it will not install.  The software uses a custom toolbox manager utility.  Seems whoever created the installer forgot to update it in the code to install into Studio 2010 but I found you can do it manually.  Here is how:

    Close Visual Studio

    Reinstall PureComponents so everything gets unregistered and then "reinstalled" even though the toolbar won't be updated yet.

    Don't open Studio until you complete these steps:

    Find the path to the PureCompenets.  Mine was:

    C:\Program Files (x86)\PureComponents\PureComponents .NET WinForms Suite V2011.1

    In there was a bin folder and a help folder.  The bin folder has the components and the help folder has toolbox commandline utility:

    Call up a command line box (CMD) window.
    Enter the following three lines adjusting the path names if needed:

    "C:\Program Files (x86)\PureComponents\PureComponents .NET WinForms Suite V2011.1\Help\toolbox.exe" /vs2010 /installdesktop "C:\Program Files (x86)\PureComponents\PureComponents .NET WinForms Suite V2011.1\bin\PureComponents.ActionSet.fw40.dll" "PureComponents"

    "C:\Program Files (x86)\PureComponents\PureComponents .NET WinForms Suite V2011.1\Help\toolbox.exe" /vs2010 /installdesktop "C:\Program Files (x86)\PureComponents\PureComponents .NET WinForms Suite V2011.1\bin\PureComponents.EntrySet.fw40.dll" "PureComponents"

    "C:\Program Files (x86)\PureComponents\PureComponents .NET WinForms Suite V2011.1\Help\toolbox.exe" /vs2010 /installdesktop "C:\Program Files (x86)\PureComponents\PureComponents .NET WinForms Suite V2011.1\bin\PureComponents.ScheduleSet.fw40.dll" "PureComponents"

    That should get your controls into the ToolBox for you if they are missing. If you want to see all the command line switches the utility has, just double click the tool box utility and a window will open to show you all the commands.   Hope this helps!!! 


    • Edited by mcnd96 Monday, March 19, 2012 3:14 AM
    •  
  • Monday, July 02, 2012 8:22 PM
     
     

    So one question since PureComponents doesn't seem to be answering my email.  I've got both VS2008 and VS2010 installed and it installed PureComponent items into both toolboxes.

    Kicker is the calendar controls that are installed in VS2010 are missing from the VS2008 toolbox after installation.'

    Are they just not available for VS2008?

  • Thursday, February 28, 2013 8:42 PM
     
     

    DO NOT buy purecomponent !

    No support, no doc no sample NOTHING !

    moreover their controls are a hell for visual designer, it is a layer above usual controls, very slow to react, sometime not refreshed properly. A must NOT have !