Cheers Sez. That's the conclusion I'd come to as well.

From: [email protected] [mailto:[email protected]] On Behalf Of 
Sezai Komur
Sent: Wednesday, 7 October 2009 4:54 PM
To: ozMOSS
Subject: Re: VS projects - Really dim question

See this comment by Carsten on the WSPBuilder codeplex project: 
http://wspbuilder.codeplex.com/Thread/View.aspx?ThreadId=17921
"The WSPBuilder do not include DLL files from Microsoft.SharePoint, this is 
hard coded into the program."
I always try and run WSPBuilder in a dev machine with SharePoint installed, you 
get other neat time-saving features provided by WSPBuilder when right clicking 
on the project in VS, things like copy to GAC, attach to IIS worker processes 
and the build options really only work if your dev machine is running 
SharePoint.
I experience the same issue as you when running WSPBuilder on a machine without 
SharePoint Installed, although it still seems to build the WSP correctly though.

Sezai.

On Wed, Oct 7, 2009 at 11:08 AM, Paul Noone 
<[email protected]<mailto:[email protected]>> 
wrote:
Oh well, my WSPs are still being correctly built.

Looks like WSPBuilder is just ignoring the VS references and looking to the GAC.

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]<mailto:[email protected]>] On Behalf 
Of Paul Noone
Sent: Wednesday, 7 October 2009 10:55 AM

To: ozMOSS
Subject: RE: VS projects - Really dim question

Yes, I added the DLL to the root bin folder. Then drag-and-dropped from the 
folder into VS so the file was added properly.

Then I deleted the old reference and added the new one by browsing to the new 
location.

So far as VS is concerned there is no problem. It's only WSPBuilder that's 
complaining for some reason.

Regards,

Paul
Online Developer, ICT
CEO Sydney

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]<mailto:[email protected]>] On Behalf 
Of Brendan Law
Sent: Wednesday, 7 October 2009 10:43 AM
To: ozMOSS
Subject: RE: VS projects - Really dim question

Have you tried removing the reference to  Microsoft.SharePoint and re adding it?

- Brendan

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]<mailto:[email protected]>] On Behalf 
Of Paul Noone
Sent: Wednesday, 7 October 2009 9:24 AM
To: ozMOSS
Subject: RE: VS projects - Really dim question

Ah, yes. I see. Thanks.

With regards to the first question, I've tried moving the DLLs outside the 
project, used different versions of them etc., but am still getting the same 
error. :\

Have never had this problem before and the references all look fine. The WSP 
builds seem OK otherwise. Just not sure what possible side effects this might 
have.

Regards,

Paul
Online Developer, ICT
CEO Sydney

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]<mailto:[email protected]>] On Behalf 
Of Trevor Andrew
Sent: Wednesday, 7 October 2009 9:08 AM
To: 'ozMOSS'
Subject: RE: VS projects - Really dim question

Hi Paul,

The second question is easy - Visual Studio always marks one of the projects in 
the solution as the "Star tup Project", and highlights it in bold. The first 
question ... umhh ... not sure ...

Cheers,
Trevor

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]<mailto:[email protected]>] On Behalf 
Of Paul Noone
Sent: Wednesday, 7 October 2009 8:51 AM
To: ozMOSS
Subject: VS projects - Really dim question

Hi all,

I've recently moved all our VS projects into subversion (yay!). As a result - 
and because we tend to do first level development on non-SharePoint servers - 
I've moved all the required DLLs into a top-level bin folder and updated the 
references.

However I have two problems. Firstly, when I rebuild any of the WSPs using WSP 
Builder I'm getting the following type of error and only for 
Microsoft.SharePoint.

Could not resolve: Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, 
PublicKeyToken=71e9bce111e9429c. Please define the -DLLReferencePath with the 
path to the referenced assemblies. However a SafeControl tag for the 
CEO.SharePoint.Branding.CEORootSiteHomePage class has been created.

Second is possibly just a dim question. Why is the CEO.SharePoint.Branding 
project always bold??

[cid:[email protected]]

Kind regards,

Paul Noone
Online Developer, ICT
CEO Sydney

ph: (02) 9568 8461
fax: (02) 9568 8483
email: 
[email protected]<mailto:[email protected]>
web: http://www.ceosyd.catholic.edu.au/


________________________________
This email is intended for the named recipient only. The information contained 
in this message may be confidential, or commercially sensitive. If you are not 
the intended recipient you must not reproduce or distribute any part of the 
email, disclose its contents to any other party, or take any action in reliance 
on it. If you have received this email in error, please contact the sender 
immediately and please delete this message completely from any systems. 
Confidentiality and legal privilege are not waived or lost by reason of 
mistaken delivery to you.

_______________________________________________
ozmoss mailing list
[email protected]<mailto:[email protected]>
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss

<<inline: image001.jpg>>

_______________________________________________
ozmoss mailing list
[email protected]
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss

Reply via email to