We're developing web parts using log4net as the logging framework. Right now we're leaving the configuration details in the web.config and will be moving the log4net.dll to the GAC manually.
For a small development team (2 devs) and an internal sharepoint installation, is that adequate? I've read about using WspBuilder, creating a setup project, a globablly scoped solutions, and so on for deployment but We really aren't going to have that much custom code. Most of our sites will be using out-of-the-box or third-party web parts along with Enterprise features like the Business Data Catalog and Reporting Services.
If you have an Enterprise license (and by association, are working for a large company), then you certainly should be doing things the proper way - you owe it to the guy that will come in after you to maintain the environment.
WSPBuilder is really as simple as it gets for packaging things up correctly, doing it the "SharePoint way". You'll need to drop the log4net dll into a folder named "GAC" in the root of your project, and make the web.config changes via the API. The terms to search for will be "web config modification" and "feature receiver".
I strongly advise that you do this for this "small" change - it'll get you used to using the tools, and more familiar/confident in how to get the work done.
I'm trying to make a web part that is managing other web parts in the solution. I need it to be able to hide other web parts based on user input. Since I can't use connections I'm trying to do this using SPLimitedWebPartManager. I got it to work but i need a double postback to get the effect, since saving the settings does not take effect before it has been loaded once more. Does any one of you know other ways of hiding web parts (in combination of using the SPLimitedWebPartManager, need the personal settings) in one postback?
One of our product will consist of multiple SharePoint solutions. Now we're wondering what would be the best way to provide an easy deployment to our customers? At the moment we deploy each solution by hand, which is OK during development process but not acceptable for our customers. For your information, we're using VSeWSS 1.3 for development and solution packaging. So how do you offer your solutions to your customers? Do you write installation scripts using STSADM commands? What other options do we have?
I'm working with a new site collection in SharePoint Server 2010 Standard created using the Blank Site template. I would like to add a Content Query Web Part to one of my web part pages, however, this web part does not show up any of the web part category lists. I have already gone into Site Collection Administration → Site Collection Features and activated the Search Server Web Parts, but the CQWP still doesn't show up. Am I missing something?
I'm prototyping the best way to dynamically connect web parts at runtime. Essentailly, the application will allow for several disparate application groups to create web parts that will be consumed within the SharePoint front end. All of the web parts will need to automatically detect consumers and providers to create connections at runtime. What we are looking to do is have webparts discover and automatically connect to other compatible webparts. When a user adds the two compatible parts to a page, the parts should be able create the appropriate connections. We have a well defined
I'm a SharePoint development beginner and I would like to develop a custom application on top of SharePoint Foundation 2010. I decided to write few visual web parts for simple logic and Silverlight... avoid one part of user administration?) and they will also define certain rights within my application. Problem? If I do write web parts (of whatever kind), how do I ensure that these same web parts are not used in other SharePoint sites as well? It would probably break the application and it could, of course, make it possible to replicate the same application but using different users. I
How can I set a web part so it will be automatically appended to a web part zone when a specific page layout is selected? The solutions I have tried so far is: Using <ZoneTemplate> under <WebPartZone> and putting my webpart in there Adding .webpart-code directly into <AllUsersWebPart> where I define the page layout, in elements.xml Put the web part on the page layouts programmatic when creating site structure (deployment script) Add a hook that hooks in and adds the web part Problems with the solutions: The web part seems to become static, and can not be removed
We have two servers: Server1: MOSS 2007 content with ESP web parts Server2: SP 2010 acting as query server We need to crawl the Server1 content from Server2, and installed ESP web parts on Server1 need to refer to Server2 as the query server. So user queries from MOSS 2007 go to the SP2010 box (where content is crawled) and return the result on the MOSS 2007 server. Please advise?
Is it possible from the MOSS 2007 OOTB web parts with no custom code of any sort to create a view of all document libraries on a given site expanded to show all folders and documents within it? Table of Contents will give you the libraries and CQWP will give you the documents but I'm looking for a combination of these I guess. I pretty sure it's not possible OOTB but thought I would ask this here just in case. Considering a DVWP to deliver the functionality but could save time if we can do this OOTB. NOTE TO SELF - Stop end users from using document libraries as folders!
I am using SharePoint Server 2007 Enterprise with Windows Server 2008 Enterprise, and I am using publishing portal template. I have created a list in top level site. And I want to use the list in a child site (e.g. adding the list to a page in child site by using Page --> Add Web Parts --> Browse), but can not find the list created in parent site in this way. Any ideas how to use the list (created in parent site) in a child site? BTW: I can use the list (created in parent site) in parent site without any issues.