Re: Web part development environment

From: Assaf (at_at_isp.com)
Date: 10/22/04 

Date: Fri, 22 Oct 2004 11:21:08 -0400

David,

Thanks for the advice (Nobel Prize nomination has been issued, you should be
hearing soon from Oslo). We too are developing for WSS.

Just to verify: is the config you describe how you are set up? With a remote
development machine? We want to verify that someone out there has in fact
succeeded to set up a 'normal' development environment before resorting to
provisioning servers all over the place.

The issues we ran into are not tire screeching show stoppers but made us
doubt that this is the right path. A couple of examples:

* After copying + referencing the Microsoft.SharePoint.dll, building a new
project created from the MS Web Part Library template without a single added
line of code results in a warning: The dependency
'Microsoft.SharePoint.Library' could not be found.

* Building a simple web part project from the SDK errored on a: The
dependency 'Microsoft.HtmlTrans.Interface' could not be found.

But heck, if you are setup this way and it's working (just verifying again)
then we'll be glad to follow.

BTW, your suggestion certainly is in line with what's described in the SDK
under topic:
"Web Part Pages and the Web Part Infrastructure"
  "Programming Tasks"
     "Creating a Basic Web Part"

5. To create a Web Part, you need to add a reference to the
Microsoft.SharePoint assembly (Microsoft.SharePoint.dll) in your Web Control
Library project. If you're working from Visual Studio .NET installed on a
server running Microsoft Windows SharePoint Services, the
Microsoft.SharePoint assembly will be registered and available from the Add
Reference dialog box. If you want to develop Web Parts on another computer,
you will need access to a server running Windows SharePoint Services. On the
server computer, copy Microsoft.SharePoint.dll from the C:\Program
Files\Common Files\Microsoft Shared\Web Server Extensions\60\ISAPI folder to
a folder on the computer where you will be developing Web Parts, and follow
the steps in this topic to add a reference. You will also need to add a
reference to System.Xml.dll to support the System.Xml.Serialization
namespace which is used to define the XML namespace for serializing custom
properties, as described later in this topic.

(http://msdn.microsoft.com/library/default.asp?url=/library/en-us/spptsdk/ht
ml/createabasicwp.asp)

- Assaf

"David McKenzie" <DavidMcKenzie@bonbon.net> wrote in message
news:eL9Am$DuEHA.4040@tk2msftngp13.phx.gbl...
> This is entirely possible, all you need is a copy of the
> Microsoft.Sharepoint.dll and the Visual Studio Web Part Templates.
> The former can be copied from your server and the latter can be
downloaded
> from Microsoft and installed on the Dev machine.
> You WILL need Visual Studio 2003, and remote debugging, while possible is
> more complicated than local debugging.
> My experience is entirely with WSS, but AFAIK that should not be an issue.
> You will really have to identify specific points of failure to get much
> help.
>
> "Assaf" <at@isp.com> wrote in message
> news:ust6AO5tEHA.3188@TK2MSFTNGP15.phx.gbl...
> > Can anyone clarify -- from firsthand experience -- whether it is
possible,
> > and what's required to develop webparts on a machine which is not a
> > SharePoint server? Our attempts to set up a dev machine (XP, no
> SharePoint)
> > have been utter failures and we're seeing totally conflicting
information
> > from MS and on the web: can't be done, copy SPS dll's locally, add
> > references to server dll's, map SPS system drives, chant incantations
> while
> > launching ... We're really pulling our hair out on this one.
> >
> > Anyone who has set up a dev machine successfully and can share the
> knowledge
> > will be nominated by us for a Nobel IT Prize.
> >
> > TIA.
> >
> > Assaf
> > assaf@donots_pam.sharemind.com
> >
> >
> >
>
>

Relevant Pages

  • Re: Proxy Management Point - Service Unavailable
    ... Verify that the Task Scheduler is enabled. ... Verify that the SQL Server has named pipes enabled. ... If you are using the IIS lockdown tool on your IIS 5 servers be sure ... I've successfully turned up> a Management Point on the Central Site server. ...
    (microsoft.public.sms.admin)
  • Exchange stops fax attachments
    ... Verify that automatic routing is enabled for email and Sharepoint. ... Open the Server Management Console. ... If the administrative groups are displayed, expand Administrative Groups, ...
    (microsoft.public.windows.server.sbs)
  • Re: FAX Problem - mail system dll is invalid
    ... To manually route a fax to someone's email, ... Verify that automatic routing is enabled for email and Sharepoint. ... Open the Server Management Console. ... If the administrative groups are displayed, expand Administrative ...
    (microsoft.public.windows.server.sbs)
  • Re: 4-way Opteron vs. Xeon-IBM X3 architecture
    ... >>>The point here is that the issue concerns both speed AND capacity. ... >As to the reference, the message header points right back in this thread, ... >>>As you may suspect, I read plenty about memory systems, and I would ... >>>from the enthusiast market and assumed that it would work in the server ...
    (comp.sys.ibm.pc.hardware.chips)
  • Re: SMS 2003 Sec. Site Management Point doesnt work
    ... Verify that the Task Scheduler is enabled. ... Verify that the Windows Management Instrumentation service is running. ... Verify that the SQL Server has named pipes enabled. ... If you are using the IIS lockdown tool on your IIS 5 servers be sure ...
    (microsoft.public.sms.admin)