|
|
Rank: Advanced Member
Joined: 6/10/2011
Posts: 37
Points: 111
Location: Belgrade
|
Hi,
I surface a new problem while developing custom apps. I create 2 separate project and for deploy target I user same site collection. The problem is when I deploy one application second disappear from site collection ME configuration page. Same thing happen when I deploy second application...the first one disappear. Is this licence limitation (I use trial licence) or I do something wrong. I want to build several ME application and deploy it at same site collection.
BR,
Alex
|
|
Rank: ME Staff
Joined: 1/12/2009
Posts: 279
Points: 408
Location: VA
|
This is a bug in the Project template. The Feature IDs do not auto-increment so you will need to update the feature ID's by hand. Once you do that, both features should show up.
Alternatively, you can just add additional EntreeApplication classes to your current project and package them in a single feature.
|
|
Rank: Advanced Member
Joined: 6/10/2011
Posts: 37
Points: 111
Location: Belgrade
|
Sorry Joe but could you give me some more explanation. Which file I edit and what part of xml I musto to update.
Alex
|
|
Rank: ME Staff
Joined: 1/12/2009
Posts: 279
Points: 408
Location: VA
|
I believe you can do this by opening the feature properties window, then in the lower left, click "manifest". Then you will need to edit that so it has a unique GUID for the feature ID in each feature.
|
|
Rank: Advanced Member
Joined: 6/10/2011
Posts: 37
Points: 111
Location: Belgrade
|
Hi, I try with this but deploy works only for same Feature id. I try to add different guids for each feature (I use guid generator) and when I do that when I run deploy for first app it works but when I try to deploy second it is failed. Here is the XML for both features: Feature 1 Code:<?xml version="1.0" encoding="utf-8"?>
<feature xmlns:dm0="http://schemas.microsoft.com/VisualStudio/2008/DslTools/Core" dslVersion="1.0.0.0" Id="95b82650-8e06-4f30-bf5b-15d5de1d9a70" featureId="cb321733-cead-4b25-82e3-9a8f22306517" imageUrl="" solutionId="00000000-0000-0000-0000-000000000000" title="My Mobile Application" version="" deploymentPath="$SharePoint.Project.FileNameWithoutExtension$_$SharePoint.Feature.FileNameWithoutExtension$" xmlns="http://schemas.microsoft.com/VisualStudio/2008/SharePointTools/FeatureModel" /> Feature 2 Code:<?xml version="1.0" encoding="utf-8"?>
<feature xmlns:dm0="http://schemas.microsoft.com/VisualStudio/2008/DslTools/Core" dslVersion="1.0.0.0" Id="cb321733-cead-4b25-82e3-9a8f22306517" featureId="cb321733-cead-4b25-82e3-9a8f22306517" imageUrl="" solutionId="00000000-0000-0000-0000-000000000000" title="My Mobile Application Feature" version="" deploymentPath="$SharePoint.Project.FileNameWithoutExtension$_$SharePoint.Feature.FileNameWithoutExtension$" xmlns="http://schemas.microsoft.com/VisualStudio/2008/SharePointTools/FeatureModel" /> In this case deploy works for both but it autoretract previos deployed feature. If I set feature id to different guids deploy fail and report this Quote:Error occurred in deployment step 'Activate Features': Feature with Id 'cb321733-cead-4b25-82e3-9a8f22306517' is not installed in this farm, and cannot be added to this scope. This id is id of second application that can deploy on farm. Thanks, Alex
|
|
Rank: ME Staff
Joined: 1/12/2009
Posts: 279
Points: 408
Location: VA
|
Try this:
1. Right-click your project and select Unload Project
2. Right-click the project again and select Edit
3. Modify the feature IDs in there to match the ones in XML
4. Save your changes
5. Right-click the project and select Reload
|
|
Rank: Advanced Member
Joined: 6/10/2011
Posts: 37
Points: 111
Location: Belgrade
|
I try with your procedure but It doesn't help. After doing all steps and try to deploy solution it give me same error at deployment step  . I have one main solution and two solution (separate ME applications) on it. Any other idea. BR, Alex
|
|
Rank: Active Member
Joined: 6/10/2009
Posts: 16
Points: 48
Location: Virginia
|
I've run into this issue a few time using the new SharePoint project template in VS 2010 and it's definitely and issue with the deployment steps for said template. What I've done in the past to resolve it is this:
(1) First, ensure that your feature have different IDs
(2) Deploy using VS deploy command - you should still see the '...not installed on this farm...' error message
(3) Open command prompt and enter the following stsadm command for each feature:
(a) stsadm -o installfeature -name <NameOfFeatureFolder> -force
(4) Features should now show up in Site Settings
I run into this issue with EVERY new SP project, what I recommend doing to get around this is to install the VS extension 'CKS Development Tools' (http://visualstudiogallery.msdn.microsoft.com/a346880f-2d29-47a6-84a2-f2d568dd6997) which will allow you to change the deployment step VS uses to 'upgrade' the solution on subsequent deployments.
|
|
|
Guest |