Just heard about the update release of the Windows SharePoint Services v3 SDK and also something called

[Via Bill Simser ] Required for every SharePoint developer: SharePoint Server 2007 SDK The Microsoft

When I try to build the State Machine Approval Workflow, I receive an error message:

Error 1 Could not create activity of type 'Microsoft.Office.Samples.ECM.Workflow.SPSMWorkflow'. System.Security.SecurityException: The source was not found, but some or all event logs could not be searched.  Inaccessible logs: Security.

  at System.Diagnostics.EventLog.FindSourceRegistration(String source, String machineName, Boolean readOnly)

  at System.Diagnostics.EventLog.SourceExists(String source, String machineName)

  at System.Diagnostics.EventLog.SourceExists(String source)

  at Microsoft.Office.Samples.ECM.Workflow.SPSMWorkflow..ctor()

The Zone of the assembly that failed was:

MyComputer F:\2007 Office System Developer Resources\ECM Starter Kit\Code Samples\Workflow\StateMachineApprovalWorkflow 1 1

Has anyone else seen this?

WSS/MOSS 2007 SDK (RTW)

Hi,

I've been waiting for these for a while because I have a number of projects that require some more details in the SDK.

My current biggest headache is that I can't get the properties of my custom field to stick once they have been saved and I try to edit them.

There does not seems to be anything changed in the RTM SDK around Custom Field Types at all, and the same errors or inconsitencies that were in the B2TR release seem to be there still. And, the date on the SDK still says December 8 (as pointed out above).

Any ideas when the next update might be and if we can up the priority of the Custom Fields areas?!

Thanks.

As promised here are the most useful resources I found on the web to get you started with SharePoint

Here is another nice post about the useful resources for the SharePoint technologies: http://blogs.msdn.com/dglover/archive/2007/01/25/getting-started-with-windows-sharepoint-services-server-2007-useful-resources.aspx...

Mark Collins wrote: "I would also like to see the documentation filled in more. It would be great if there was a way for the community to contribute to it."

If I want documentation written by a bunch of people I've never met, I'll set up a Linux server and Ruby on Rails.

Getting a medium-sized MOSS 2007 environment up and running will set you back at least $20,000 in software alone, by the time you buy Server 2003, SQL Server, CALs, some copies of SharePoint Designer, etc.  Add in redundant servers, Forms Server or Project and you'll pass $50,000 before you know it.  At a big company like the one I work at, you'll pay six figures every year to Microsoft, and that's just the servers.  It doesn't include client software and desktop licenses.

Now look at the product.  Nothing is documented.

I'm trying to show the Notes developers in my group how to develop software under ASP.NET and SharePoint, and I don't have any references to work from?  They are even more outraged than me.  MSDN is a big site full of blank pages and placeholders, as far as they can see.

Attention Microsoft SharePoint team: This is not beta anymore.  This is (supposedly) RELEASE SOFTWARE.  It should have been documented months ago.  Whoever is in charge of MSDN for SharePoint should be read the riot act.  Better yet, just show them the door.

Michael: "they might have just accidently linked to the old version that was already out there"

None of the documentation is on msdn.com either.  As far as anyone can see, it was simply never written.

The deafening silence from the Office Developer Documentation team speaks volumes.  Randall Isenhour announced the "release" SDK, but apparently has nothing to say about the complete lack of API documentation.

The state of documentation in WSS and OSS is disgraceful, and unworthy of a professional development team.  You guys have produced a fantastic product with awesome capabilities, then utterly failed to provide the information to allow the development community to build on your platform.

Specific areas I would like to see adressed is the Web Service reference in WSS SDK.

Functions undocumented, sample code not syntactically correct, and pre-release caveats all over it.  The same applies to the OSS Web service reference.

Would anyone here like to respond to Mike FitzMaurice blog posting below?

http://blogs.msdn.com/mikefitz/archive/2006/11/17/the-rtm-sdks-will-be-downloadable-on-november-28th-2006.aspx

Reality is obviously not troubling the IT Evangelist community...I wonder if he has read the SDK...

The areas that I need to be able to use on the SDK's are lacking of necessary documentation or implementation syntax for a developer. I have been beating my head against a wall looking for any information that might be available for workflow development in VS 2005, but the documentation is severely lacking and, as JSConsult stated, disgraceful.

MOSS 2007 and WSS 3.0 have tremendous potential, but getting at it is still next to impossible! I'm almost fed-up with the lack of useful resources. Usually I can go out and purchase a book with decent information, but in this case, no one seems to know everything that can be done with this platform.

Please, in order for developers to embrace MOSS, WE NEED DOCUMENTATION that is thourough and complete!

thank you http://www.parcakontorbayiniz.comthank">http://www.parcakontorbayiniz.comthank you http://www.parcakontorbayiniz.com...