Multiple solutions using shared DLLs can cause havoc when individual solutions are retracted

Charles Lee
  • Multiple solutions using shared DLLs can cause havoc when individual solutions are retracted Charles Lee

    Problem: Multiple solutions using shared dll's can cause havoc when individual solutions are retracted.

    Example: You have a web part helper dll used by all your web part code. If you retract a solution containing a reference to this dll then the SafeControl entry is removed from the appropriate web application and all your web parts start to fail. Or even better, the dll is removed from the GAC altogether.

    Solution: I don't know? You tell me.

  • Yes, That's a common issue in SharePoint deployment. My Solution is to change the version number for helper dll-s. So even you have multiple helper dll-s in GAC that should not be a big issue. Tip:SolutionInfo

  • When you have common/shared components, like the helper DLL you talk about, that get used across multiple solutions within you organization. My recommendation is to package these up as a 'framework solution' that is deployed to the servers indendently of the 'feature based solutions'.

    This way you 'feature solutions' are developed in the knowledge that the 'framework' is always available.

    SharePoint always will retract/remove what you added in a solution package, unforunately it does not have anything built in to detect shared components.

Related questions and answers
  • 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 <... 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... the page. We do have hooks for setting default page layout based on where in the structure the page is created, here we can append the web part as well, but then the web part will only be added if you create

  • I have a webpart that is part of a larger solution, deployed as a WSP using WSPBuilder. I can see the SafeControl entry in the web.config and can see that the assembly has deployed to the GAC. The solution reports as installed OK in Central Admin and the feature is activated at the site collection. When I attempt to add the webpart to a page, I'm getting an error stating that the "Type could not be found or is not registered as safe." I have removed this solution from MOSS and completely re-created the webpart, in case I've messed up GUIDs or something. I'm not sure what to check next. Any

  • appropriately. I can see the status change on the Solution Management page from deploying to deployed. There are no errors in the trace logs or event viewers. However, the 12 hive only contains files... added another server to the farm, moved the central admin with the stsadm tool, and removed the old server from the farm. Here is what I have tried: Deployed to two other farms: successfully deployed..., we were lucky enough to still have the soon to be decommisioned server that previously ran Central Admin (Server1). So, I added the server to the farm. Removed the Central Admin from the new Server

  • I've been hitting my head against a wall on this one for the last couple of days. I have a pretty simple requirement but I cant see how it can be achieved within a Sandboxed solution. I'm depressed because I think its a critical limitation that will cause me grief in future solutions too. Here is the scenario. I have an existing site and I want to be able to activate a feature, and then as part of that activation, drop web parts onto some specific pages. In my case I want to be able to drop it onto the "AllItems.aspx" page of a list, but I'm equally having trouble adding

  • My problem precisely and concisely is that I developed a simple web part to display OOTB Surveys on the page (Which means user can answer and submit the survey through my web part). It works correctly. BUT when I add the web part two times, then, User will not be able to submit any of them. Simply because when s/he answer the first survey and click Submit-Button, the required field validation will fire on the other web part and requesting to be filled. Scenario: (I hope those steps give you better understanding of my case) 1- Assume that I add my SurveyViewer web part to display Voting

  • " maxRequestLength="104856" /> After searching I found https://stackoverflow.com/questions/1580085/show-webpage-has-expired-on-back-button. Well, obviously I cant use GET because I am developing a web part NOT a page. Also, it is not possible to oblige the clients to change their forms from POST to GET just to use my little web part (I think you understand me). I put a breakpoint inside the web...-scope is only within the web part NOT the full page. Also, I do not want to use any AJAX-controls. Update: I was told that the only way to get rid of "Webpage has expired" error is either by: Using

  • but I keep running into security related obstacles. Since timerjobs are child objects of SPWebApplication, they are stored in the config database. If you have set up your farm properly in such a way that the App pool user for your content web application does not have write access to the Config database, you can't create new TimerJobDefinitions from code that runs in your content web app. A bad... the Central Admin app pool account can write to the config database But then we lose the whole point - I want my site collection administrators to be able to manage the schedule! The only alternative solution

  • 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?

  • . The only significant thing to change on the server between yesterday and today was the installation of the Citrix Web Interface for SharePoint webparts. UPDATE: I also receive the following error when starting Central Administration from the Start Menu (Start -> Microsoft Office Server -> SharePoint 3.0 Central Administration) A failure occurred when accessing the HKEY_LOCAL_MACHINE\Software\Microsoft\Shared Tools\Web Server Extensions\12.0\WSS registry key. Repair this product by selecting it from the Add/Remove Programs menu. If I access Central Administration via a browser

Data information