0

I am getting this familiar error while trying to deploy my solution through visula studio. Earlier I used powershell scripts but this time I am little skeptical. Here is the scenario:

I am Working on a development server, which is shared by a couple of team members.

I have taken the latest code from TFS, went offline, ie I am not connected to TFS

I made a new site through central admin and i deployed my solution to it using Visual studio. This is where i Get my error.

When i checked in Central admin, I do see the already exixting solution.

What I want to know is, if I deploy it using power shell or force attribute, will it affect the other people's exixting sites?

Improve this question

1 Answer 1

Reset to default
1

Since a solution can not be scoped to anything more granular than a Web Application, the feature definition will be updated for all web applications that uses the particular feature.

But the other users will have to re-enable the feature to get the new modules etc. from the feature. Another issue is with feature receivers where your feature will update the code behind in the .dll placed in GAC for all users.

Improve this answer
7
  • So what approcah should I follow, if I want to add and test some additonal functionality, Like in my case , I want to add expand all and Collapse all Button for the tree view nodes in the website. but I dont want to imapact other team members sites.
    – Deepika
    Jul 19, 2013 at 6:56
  • I think the idea of a Shared development server is not the best from the beginning. One approach would be to set up one dev server for each team member, to separate your code. You could possibly use the same SQL Server and use the same service applications though (but it is a trickier setup).
    – Robert Lindgren
    Jul 19, 2013 at 6:59
  • yes, I know!! But this is what we are provided to wok upon in my new project, so cannot do any reconfiguration.
    – Deepika
    Jul 19, 2013 at 7:00
  • 1
    Then it is tricky! Since you share the code base and the features it is hard to separate. One, not so good but working, approach would be to create new features where you test out functionality and when satisfied, you move that code to one of the other features that the other team members also uses
    – Robert Lindgren
    Jul 19, 2013 at 7:02
  • Can you help me with the suggestion you proveided? any Link to the steps explaning?. i have added a new webpart implementing the functionality but I am clueless as to how to create feature for that?
    – Deepika
    Jul 19, 2013 at 9:07

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.