|
|
Rank: Advanced Member
Joined: 9/21/2010
Posts: 33
Points: 99
Location: Richardson, Tx
|
Hey folks,
I am trying to create three seperate ME applications in VS 2010. The code works and builds, but there is a problem with packaging. For some reason, all three application projects behqve as though they are one and the same. As a test I added a new empty Mobile Entree application project to the solution and it also acted the same.
I have not yet tracked down the issue, but I suspect it has something to do with a solution ID or something in the default templates.
Anyone have any thoughts on the matter?
UPDATE:
It was indeed that issue. The FeatureID and PackageID GUIDs for every project was the same. As soon as I unloaded the projects, changed the guids, then reploaded the projects, everything worked fine.
I will see if I can fix the Project template and report back.
|
|
Rank: ME Staff
Joined: 1/12/2009
Posts: 279
Points: 408
Location: VA
|
Ahh, yeah.. those GUIDs are not being dynamically generated. We will also take a look at updating those.
|
|
Rank: Advanced Member
Joined: 9/21/2010
Posts: 33
Points: 99
Location: Richardson, Tx
|
for reference, I replaced lines 60 - 71 of the Template2010.csproj file with the following Quote: <ItemGroup> <None Include="Features\MobileFeature\MobileFeature.feature"> <FeatureId>$guid1</FeatureId> </None> <None Include="key.snk" /> <None Include="Package\Package.package"> <PackageId>$guid2</PackageId> </None> <None Include="Package\Package.Template.xml"> <DependentUpon>Package.package</DependentUpon> </None> </ItemGroup> I tested it out and it works fine now
|
|
Rank: ME Staff
Joined: 1/12/2009
Posts: 279
Points: 408
Location: VA
|
Awesome, we will update the templates and push them out to Codeplex. Thanks for the help.
-joe
|
|
Rank: Advanced Member
Joined: 9/21/2010
Posts: 33
Points: 99
Location: Richardson, Tx
|
Not a problem. Also note that the featureID GUID and the packageID GUID are hardcoded in the MobileFeature.feature. In addition the solutionID guids and the feature reference guid are all hard coded in the Package.package file. I am looking into the process for changing those in the template.
|
|
Rank: Advanced Member
Joined: 9/21/2010
Posts: 33
Points: 99
Location: Richardson, Tx
|
I have made that change.. here is the layout for the MobileFeature.feature Quote:
<?xml version="1.0" encoding="utf-8"?>
<feature xmlns:dm0="http://schemas.microsoft.com/VisualStudio/2008/DslTools/Core"
dslVersion="1.0.0.0"
Id="$guid1$"
featureId="$guid1$"
imageUrl=""
title="$safeprojectname$"
version=""
deploymentPath="$SharePoint.Project.FileNameWithoutExtension$_$SharePoint.Feature.FileNameWithoutExtension$"
xmlns="http://schemas.microsoft.com/VisualStudio/2008/SharePointTools/FeatureModel" />
and here is the layout for Package.package Quote:<?xml version="1.0" encoding="utf-8"?> <package xmlns:dm0="http://schemas.microsoft.com/VisualStudio/2008/DslTools/Core" dslVersion="1.0.0.0" Id="$guid2$" solutionId="$guid2$" resetWebServer="false" name="$safeprojectname$" xmlns="http://schemas.microsoft.com/VisualStudio/2008/SharePointTools/PackageModel"> <features> <featureReference itemId="$guid1$" /> </features> </package> in addition, the template content section of the MyTemplate.vstemplate should look like this: Quote: <TemplateContent> <Project TargetFileName="Template2010.csproj" File="Template2010.csproj" ReplaceParameters="true"> <Folder Name="Features" TargetFolderName="Features"> <Folder Name="MobileFeature" TargetFolderName="MobileFeature"> <ProjectItem ReplaceParameters="true" TargetFileName="MobileFeature.feature">MobileFeature.feature</ProjectItem> <ProjectItem ReplaceParameters="true" TargetFileName="MobileFeature.Template.xml">MobileFeature.Template.xml</ProjectItem> </Folder> </Folder> <ProjectItem ReplaceParameters="false" TargetFileName="key.snk">key.snk</ProjectItem> <ProjectItem ReplaceParameters="true" TargetFileName="MobileApplication.cs">MobileApplication.cs</ProjectItem> <Folder Name="Package" TargetFolderName="Package"> <ProjectItem ReplaceParameters="true" TargetFileName="Package.package">Package.package</ProjectItem> <ProjectItem ReplaceParameters="true" TargetFileName="Package.Template.xml">Package.Template.xml</ProjectItem> </Folder> <Folder Name="Properties" TargetFolderName="Properties"> <ProjectItem ReplaceParameters="true" TargetFileName="AssemblyInfo.cs">AssemblyInfo.cs</ProjectItem> </Folder> </Project> </TemplateContent> I can send the completed zip file to ya'll if you like. Just send me an email.
|
|
Rank: ME Staff
Joined: 1/12/2009
Posts: 279
Points: 408
Location: VA
|
Yeah, send it to me.support@h3s-inc.com. That would be much appreciated.
|
|
Rank: Advanced Member
Joined: 6/10/2011
Posts: 37
Points: 111
Location: Belgrade
|
joe wrote:Awesome, we will update the templates and push them out to Codeplex. Thanks for the help.
-joe Joe question for this. Is there updated solution on codeplex that correct following issue. Still I have the problem with deployent. Alex
|
|
Rank: ME Staff
Joined: 1/12/2009
Posts: 279
Points: 408
Location: VA
|
I just checked and Codeplex was not updated with this. I have now uploaded this new version, and you can download it from the same place. http://mesdk.codeplex.comYou may want to just follow his directions since you already have your projects built. Otherwise you will need to migrate them to new projects based on this new template.
|
|
Rank: Advanced Member
Joined: 6/10/2011
Posts: 37
Points: 111
Location: Belgrade
|
Thanks Joe,
It is no problem to create new applications based on new template bacause it is only for demonstration purpose to our client.
Alex
|
|
Rank: Advanced Member
Joined: 6/10/2011
Posts: 37
Points: 111
Location: Belgrade
|
Joe thanks for uploading template It's solve my issues and I migrate my applications with success.
Alex
|
|
|
Guest |