I have a UWP app and a WPF console app for special SDK (can't work in UWP). Linked these apps with default bridge (aka FullTrust). Then I package them with default package project for Windows apps.
But when I tried to upload my .msixupload file to Submission in Microsoft Store, I got this message:
Package acceptance validation error: We encountered a fatal error while parsing the package: Value cannot be null. Parameter name: source. Try again or upload a new package.
Screenshot of error
Apps works fine in release. But can't upload a store.
This solution does not help
Found solution.
In package project file .wapproj, delete PackageReference with Microsoft.Windows.SDK.BuildTools
<Project>
...
<ItemGroup>
<PackageReference Include="Microsoft.Windows.SDK.BuildTools" Version="10.0.19041.8" PrivateAssets="all" />
</ItemGroup>
...
</Project>
Related
I set a build for a react web app in azure devops and another one for a web api application (c#). I would like to copy the output of the react build in the web api project before release them in Azure. I tried with a copy task but i failed due to the web api application output (it's a zip). Help would be very appreciated.
On the project I'm on right now, this is solved by
1. building the front-end before building the web app project, and
2. including the react-output-folder in the visual studio project, but using a wildcard, not each file:
<Content Include="webstorybook\*" />
By doing that, the files should be included in the published .zip file. Hope it works for you, too.
I am trying to deploy a Salesforce lightning coponent thorugh Eclipse from one dev org to another but I am receiving below errors.
I am able to succesfully install the components through an unmanaged package but would like to konw if it is possible to deploy lightning components through Eclipse
Please see attached images for the errors.
INVALID_CROSS_REFERENCE_KEY ERROR
Eclipse unknown data type
For deploying aura components follow the steps below:
1) Open Package.xml in Ecllipse
2) Add following code:
<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
<types>
<members>*</members>
<name>AuraDefinitionBundle</name>
</types>
<version>35.0</version>
</Package>
3) Refresh your project from server
Regards,
Ajay
I was able to deploy the complete aura folder to sandbox, i think you need to create a new project with aura components and its dependencies and try to deploy to the sandox.
I'm a developer without access to the build server. I am attempting to configure my silverlight project to build on the build server, without installed the Silverlight 5.0 SDK. I can place all of the SDK files into a source folder, so I just need to redirect MSBuild to find them.
I've attempted to do this by editting the FrameworkRegistryBase tag in Microsoft.Silverlight.CSharp.targets file, but am still getting the same error message:
"The Silverlight 4 SDK is not installed".
Can you tell me where the path to the SDK can be overridden?
Thanks
I have a Visual Studio 2010 solution file with a number of projects in it. There is a mix of Silverlight projects (acting as modules), the Silverlight Shell project and a number of RIA services.
When using TFS 2010 to perform the build, it always fails because the proxy classes generated by the RIA services have not been built first. The only solution I have seen so far is to manually change the build order in my .sln file. No thanks, there are loads of projects.
Rather than break the solution up in to client side and server side solution, I'd like to find a better solution.
Apparently MSBuild 4 ignores the build order in the .sln file.
Does anyone have any ideas/suggestions?
Thank you,
The simplest way I've found is to declare explicitly the dependency between Silverlight project and the project that is hosting RIA service.
You have to open in a text editor your Silverlight project file and add a fragment to it:
<ItemGroup>
<ProjectReference Include="..\Path\Your.Hosting.Project\Your.Hosting.Project.csproj">
<ReferenceOutputAssembly>false</ReferenceOutputAssembly>
</ProjectReference>
</ItemGroup>
This will tell msbuild to build your web service before building your Silverlight app. And it will work only when building with msbuild, VS will throw an error.
To get it built in Visual Studio also, you have to wrap this fragment in a Target and add it to InitialTargets in Project node:
<Target Name="MySpecialReferences">
<ItemGroup>
<ProjectReference Include="..\Path\Your.Hosting.Project\Your.Hosting.Project.csproj">
<ReferenceOutputAssembly>false</ReferenceOutputAssembly>
</ProjectReference>
</ItemGroup>
</Target>
<Project ... InitialTargets="MySpecialReferences" ... >
Visual Studio 2010 will skip this target now but msbuild will use to change built order of projects.
This definitely doesn't seem to be the "proper" solution, but as an interim option what about checking in the generated Generated_Code\*.g.cs files for your RIA services present in your Silverlight projects? If people check in the up-to-date version along with the matching updates to their DomainService classes, all should build as expected.
Below is a sample from an MS Build script that we're using in our project. Basically, we've labelled our web project (containing the RIA services) as a priority project and are building it first.
Please note that the 1st XML tag should be located somewhere in the environment setup stage.
<ItemGroup>
<!-- use this collection to control project build order, projects listed in this array are removed from the current build queue and pushed in the front before compilation-->
<InitialBuildProjects Include="MyProject.Web.RiaServices" />
</ItemGroup>
<ItemGroup>
<PriorityProjects Include="$(ProjectRootDirPath)\Sources\%(InitialBuildProjects.Identity)\%(InitialBuildProjects.Identity).csproj" />
<RemainingSourceProjects Include="$(ProjectRootDirPath)\Sources\**\*.csproj"
Exclude="#(PriorityProjects)" />
<SLTestProjects Include="$(ProjectRootDirPath)\Tests\*.Web\*.Web.csproj" />
<BuildQueue Include="#(PriorityProjects);#(RemainingSourceProjects);#(SLTestProjects)" />
</ItemGroup>
Works for us in private builds + on our TeamCity server.
Does this help ?
I followed this excellent tutorial but, as it doensn't cover the deployment part, I tried to do it by myself.
So, I installed Springsource Tool Suite in Ubuntu.
Then, I create a "demo1" Roo project.
Next, with the built-in Roo Shell, I taped the following commands:
persistence setup --provider DATANUCLEUS --database HYPERSONIC_IN_MEMORY
entity --class ~.server.domain.Employee
field string --fieldName firstName --sizeMin 3 --sizeMax 20
field string --fieldName lastName --sizeMin 3 --sizeMax 20
gwt setup
After I checked "Use Google Webkit" in "Webkit Options", the project ran perfectly!
Then, to deploy the application to the App Engine, I taped the following command:
persistence setup –database GOOGLE_APP_ENGINE –provider DATANUCLEUS
which runs without any problem.
Then, i setup the AppEngine options (Application name and version ...) and clicked on the "Deploy App Engine Project" icon.
A popup shows and asks for the project name, email and password.
I gave all these information and clicked on "Deploy".
Unhopefully, an error occured and a popup showed with the following error message:
GWT compilation failed
And in the console, I got the following error:
Compiling module com.springsource.demo1.gwt.ApplicationCommon
[ERROR] Module has no entry points defined
I think that the problem is that GWT can't find the war file ...
Anyone succeded in deploying a GWT/Roo application by clicking on the "Deploy" icon?
Thank you very much,
Regards.
What you need to do is go to the Google -> Webtool Kit Settings... and remove ApplicationCommon from the Entry Point Modules list, and you probably need to remove some more, so only the configuration file with the Entry point remains.
Some background: The error is generated by the GWT compiler. When deploying GWT compiles the Java source to JavaScript. GWT uses module files with the extension: .gwt.xml which contain configuration information for the compiler. In at least one of these configuration files an entry point must be specified. By default the Webtool Kit Settings contain all those gwt.xml files from your project (there are probably 4), while only those with an entry point should be specified.
What version of STS were you using? I think this may be fixed with STS 2.3.3.M2...