Moss 2007
-
Hi, I would be creating a collaborative site in MOSS 2007. I need to have custom webparts and pagelayouts created for it. I have never created a solution from scratch in VS for it although I can create webparts and masterpages/pagelayouts. This might get migrated to Sharepoint 2010 early next year. Can you give me an idea or steer off to suitable reference stuff as to the VS solution design and best practices. Also how to create wsp package to be directly installed in farm. Many Thanks,
-
Hi, I would be creating a collaborative site in MOSS 2007. I need to have custom webparts and pagelayouts created for it. I have never created a solution from scratch in VS for it although I can create webparts and masterpages/pagelayouts. This might get migrated to Sharepoint 2010 early next year. Can you give me an idea or steer off to suitable reference stuff as to the VS solution design and best practices. Also how to create wsp package to be directly installed in farm. Many Thanks,
For building the wsp you'll want to have WSPBuilder[^]. This will also install some project templates that could be helpful for you. WSPBuilder - Walkthrough of the Visual Studio Add-in[^]
I know the language. I've read a book. - _Madmatt
-
For building the wsp you'll want to have WSPBuilder[^]. This will also install some project templates that could be helpful for you. WSPBuilder - Walkthrough of the Visual Studio Add-in[^]
I know the language. I've read a book. - _Madmatt
-
For building the wsp you'll want to have WSPBuilder[^]. This will also install some project templates that could be helpful for you. WSPBuilder - Walkthrough of the Visual Studio Add-in[^]
I know the language. I've read a book. - _Madmatt
While using the WSP builder you can deploy your web parts in sharepoint 2007 but you also required the solution package for your webparts which includes all the stuff and allow you to deploy in a one go (known as CAB files -Technically).
-
While using the WSP builder you can deploy your web parts in sharepoint 2007 but you also required the solution package for your webparts which includes all the stuff and allow you to deploy in a one go (known as CAB files -Technically).
WSPBuilder creates a solution file known technically as a SharePoint Solution Package, not a CAB file. If you are going to respond then at least know what your talking about.
I know the language. I've read a book. - _Madmatt
-
WSPBuilder creates a solution file known technically as a SharePoint Solution Package, not a CAB file. If you are going to respond then at least know what your talking about.
I know the language. I've read a book. - _Madmatt
Thanks for letting me know what i have to reply. As per my understanding and the others related to solution packages, if you are using WSP bulider it created the whole package and deployed it into the farm, but my concern is how a person can deploy the same on production sever. It is recommened by the Microsoft that on the production server only contains the framework and the development server can contains the rest of the things. As the WSP builder is the 3rd party tool which allow you to create the webparts, event handlers and other stuff and allow you to deploy the same in the farm it ask you to provide the scope for the same. But it will not give or generate any code which you take and deploy on the prodcution serve. Person have to make the CAB file to deploy it on production server. I appreaticate your response but i would alos request you to please make your words in such a way that it would be helpful to others and it should not hurt the others.I hope you understand what i want to say in a proper words..
-
Thanks for letting me know what i have to reply. As per my understanding and the others related to solution packages, if you are using WSP bulider it created the whole package and deployed it into the farm, but my concern is how a person can deploy the same on production sever. It is recommened by the Microsoft that on the production server only contains the framework and the development server can contains the rest of the things. As the WSP builder is the 3rd party tool which allow you to create the webparts, event handlers and other stuff and allow you to deploy the same in the farm it ask you to provide the scope for the same. But it will not give or generate any code which you take and deploy on the prodcution serve. Person have to make the CAB file to deploy it on production server. I appreaticate your response but i would alos request you to please make your words in such a way that it would be helpful to others and it should not hurt the others.I hope you understand what i want to say in a proper words..
Again, you have no idea what you are talking about. WSPBuilder does not create WebParts, or event handlers, and the like. If you actually looked at the tool and the documentation you may understand it only creates the template in Visual Studio, it is up to you to add code and anything else required. Likewise, WSPBuild can be used to both build and deploy in a development environment, however it DOES build a solution package that can be deployed to other servers. Before responding to any other posts please understand the tools and technology. You have so far only shown your ignorance and have added nothing but distraction.
I know the language. I've read a book. - _Madmatt
-
Again, you have no idea what you are talking about. WSPBuilder does not create WebParts, or event handlers, and the like. If you actually looked at the tool and the documentation you may understand it only creates the template in Visual Studio, it is up to you to add code and anything else required. Likewise, WSPBuild can be used to both build and deploy in a development environment, however it DOES build a solution package that can be deployed to other servers. Before responding to any other posts please understand the tools and technology. You have so far only shown your ignorance and have added nothing but distraction.
I know the language. I've read a book. - _Madmatt
Thanks Mark for your prompt response.