Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Visual Studio Extensions for SharePoint 3.0

  Asked By: Michael    Date: Jun 13    Category: Sharepoint    Views: 1189

I am trying to use the VS Extensions to write a webpart for SharePoint
3.0. I select the WebPart template, build my Hello World webpart and
hit F5. Hey Presto my WebPart appears in my SP site!....

However, the joy is short lived because I then go back to my code and
make some changes. I then hit F5 again but this time it fails at the
deploy step with "Object Reference not set to an intstance of an

Any ideas? I found one post about somebody who had the same problem but
no solution as yet....



4 Answers Found

Answer #1    Answered By: Kalpana Ghatge     Answered On: Jun 13

I'm having the same problem...press F5, builds OK, but fails during
the deploying stage with "Object Reference not set to an instance of
an object".

Does anyone know if there's a log that gets created when F5 is
pressed? It would be nice to see some details of what's going on
during the build/deploy stage.

Answer #2    Answered By: Bobbie Rodgers     Answered On: Jun 13

I'm another person with the same problem... build  and deploy the
SharePoint solution once and it works great. Try it again, "object
reference not set to an instance of an object."

I'm trying this with the list definition, site definition, and web
part templates that are included in the Visusal Studio Extensions for
Sharepoint Server.

What's especially strange is that this was working fine for me a few
weeks ago... I could repeatedly re-deploy web parts and site/list
definitions by just hitting F5. Now i have to retract and delete the
solution to debug, and that is a huge pain.

i really hope someone can help.

Answer #3    Answered By: Bhumi Gokhale     Answered On: Jun 13

I recommend avoiding VSeWSS at nearly all costs. It is riddled with bad
practices and non-extensible.

Answer #4    Answered By: Davon Henson     Answered On: Jun 13

If you are redeploying the same instance of a list, site, webpart  with
updated code this should work. But if you are using the original project to
deploy something that is essentially new then this is the error that you
will get. Before you deploy the new item change the GUID that is in the
project properties. Otherwise SharePoint will think it is a new version of
something that is already deployed and not give you a new instance. Also
make sure that the target URL is filled out properly in the Project

BTW, this is one of the reasons that I don't use the VS Extensions. I do my
lists, sites, and webparts the old fashion way, in code. When I'm all done
testing I write  a Solution deployment Manifest and deploy the solution. I
find the extensions  have too many issues and are too time consuming.

Didn't find what you were looking for? Find more on Visual Studio Extensions for SharePoint 3.0 Or get search suggestion and latest updates.