Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
At least two of the SDK Samples do not work. Does Microsoft want us to try and create Addins during the Beta period? RRS feed

 > 

  • General discussion

  • Discussion
    Sign in to vote
    0
    Sign in to vote

    I can now confirm that two of the samples in the SDK do not work.  I was able to get the Provider sample to work after some investigation and a simple bug fix.  And I am able to get parts of the Remote Access sample to work if I install my addin on my development server at C:\Program Files\Windows Server\Bin\WebApps\RemoteAccess and

    • move the dll for the addin to C:\Program Files\Windows Server\Bin\WebApps\RemoteAccess\bin
    • delete the web.config file for the addin project.
    • Ensure that the Guid in the webaddin.xml document is unique.

    It has taken me over 4 days to get two samples partially working and I have had to hack and fix the samples just to get that far.  I also noticed that some public classes are missing from the documentation provided.  I know because they show up in .Net Reflector.    I wanted others in the forums to read this so that they do not waste their time on the samples.  As for me I am done with them until they are updated.

    To the Microsoft folks:

    I understand that the samples will always be behind the development of the framework but you could occasionally post some updates to the samples on the Windows Home Server blog or in this forum.  I am very excited by the new Beta and I still plan on using the beta and reporting bugs but I thought that having developers create addins was also a part of the Beta process (Hence the existance of this forum).

    So the question I would like answered is does the WHS development team want developers to attempt to create addins during the Vail Beta period?

    Thanks

     

    Thursday, June 24, 2010 3:27 AM

All replies

  • Discussion
    Sign in to vote
    0
    Sign in to vote

    As you've already noted, the SDK lags behind the reality of Vail. Unfortunately that's the nature of a beta; the SDK can't really be updated until new or changed features are pinned down fairly well, and that means updates will be pretty infrequent.

    Please do continue to try creating add-ins. :)

    I'm not on the WHS team, I just post a lot. :)
    Thursday, June 24, 2010 1:05 PM
    Moderator
  • Discussion
    Sign in to vote
    0
    Sign in to vote

    I thought I would share this reply to my comment about this issue to Microsoft Connect.  No date given but hopefully SOON! :)

    Greetings from Microsoft Connect!

    This notification was generated for feedback item: Please update the SDK samples so they work and update the Help information so that all of the framework classes appear. which you submitted at the Microsoft Connect site.

    Hello Zaliis!

    Thank you very much for your feedback!
    We know that there are some issues in the SDK that we gradually eliminate.
    We are currently preparing a new version of the SDK to accommodate a lot of changes that happened over the last few weeks in the product. We will post a new version of the SDK together with the next public pre-release of the main product.
    With the new version we will also announce that we have a common extensibility story for the Small Business Server Code Name “Aurora” together with “Vail”. The new SDK will be the “Windows Server Solutions SDK” with many updates. Please stay tuned.

    But we would really like to thank you again for your feedback. This is very valuable for us and we constantly try to improve our work – feedback is therefore essential!

    Best regards,
    Windows Home Server Extensibility Team

    Tuesday, August 3, 2010 4:19 AM