how do you package up silverlight dlls into a xap file? - silverlight

Just updated build server with rc0 and surprise no chiron. Wondering how you package up a xap file without chiron.

Hey Brian, you can get chiron from http://www.codeplex.com/sdlsdk -- it was decided to be removed from the SL SDK core tools, but is still a part of the DLR SDK which is available.

More specifically you can still use MSBuild. The targets should be located at C:\program files\MSBuild\Microsoft\Silverlight\v2.0 if you need to look at them or modify...your .csproj(or.vbproj) can also have pre/post build tasks for MSBuild as well.

Related

How to bundle windows visual studio VSIX with other built application?

I found that the windows visual studio extension is targeted to .net framework and only .net framework (which seems not clearly described in the docs?), after switching our custom mono debugger extension to .net 7.0, with framework not compatible (between vsix project's .net framework 4.8 and debugger project's .net 7.0) error when building the vsix project.
If I switch the debugger project target back to .net framework 4.8 then I can build the extension along with the debugger and create a vsix bundle them togeter successfully.
I tried the previewing visual studio extensibility tools: the out-of-process solution, but the out-of-process way seems not have access to the dte object, thus no way to send the debug adapter launch command. If I use the in-process solution, then we head back to the .net framework target :(
The mono debugger extension is a "3rd party executable file" that launched by visual studio debug adapter. If I manually paste the .net 7.0 version mono debugger to the extension install location, the extension can still work with the debugger. I manage the debugger project and the vsix project within a solution is for easier project management only, in fact they are not referenced directly in code.
I switched our mono debugger project to .net 7.0 is for trying to upgrade our toolset to the newest unified framework (every other tool in our team are upgraded to .net 7.0).
TL;DR, how can we bundle a none .net framework targeted project along with a windows visual studio extension, which is targeted to .net framework only? Or how can we integrate/bundle/add built exe,dlls into the vsix container?
There are some solutions from other stackoverflow answers such as add dlls using vsixmanifest, but it can only add dll file, and the way it handle asset file seems not quite right, it just copy the dll to vsix project folder once, meaning it won't get updated when the dll's project rebuild.
Here I managed to bundle the files in a wonky way:
I create a publish folder under vsix project folder,
then copy the published debugger project file to it, add them as existing file to vsix project, and configure them as vsix content, copy to vsix,
then add a pre-build event for the vsix project, publishing our debugger project and output to this publish folder.
With process above, I can package the published file into vsix when trigger vsix project build.
For anyone have similar issue, you can have a try.

Where can I download RiaServices.msi nowadays?

Where can I download RiaServices.msi from the web, after Microsoft removed it?
I need to prepare a new virtual machine to host a legacy Silverlight application.
Thanks!
As far as I know, downloading ria.services separately may not be easy to find at the moment, you can use NuGet to install it.
After the hint from #Jiayao, I decided to forget about the RiaServices.msi installer and manually copy the necessary files to the target host machine, where the Silverlight app was published.
Luckily the files simply need to be copied to the silverlight "bin" folder.
The files I copied were:
System.ServiceModel.DomainServices.Client.dll
System.ServiceModel.DomainServices.Client.Web.dll
System.ServiceModel.DomainServices.Hosting.dll
System.ServiceModel.DomainServices.Server.dll
These libraries are available in the "lib" folder of riaservices.silverlight.4.2.0 and riaservices.server.4.2.0 NuGet packages. You can download the packages, rename the .nupkg files to .zip and extract them.
If I have the chance to compile the Silverlight application from the source, I plan to add these NuGet packages as dependencies of the project, so they can be normally deployed within the Silverlight application.

Why does my Windows Application Packaging project think my solution is a net 6 solution?

My solution is a net 5 solution. I've been through all of the nuget packages to make sure they are all 'net5' compatible and checked that all the .csproj target frameworks do indeed say net5.0 yet when I go to package my application (MyProj.Installer - Windows packaging application) it shows me a warning:
Warning NU1702 ProjectReference 'C:\Users\rich-\source\repos\MyProjGit\MyProj\MyProj.csproj' was resolved using '.NETCoreApp,Version=v6.0' instead of the project target framework '.NETFramework,Version=v4.5.1'. This project may not be fully compatible with your project. MyProj.Installer C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets 1718
I have no idea where it is getting .NETFramework,Version=v4.5.1 from as the oldest version my project has ever been is 4.7.2 but more to the point it thinks it is a net6 application when it is a net5 application.
It goes through and packages the app as an msix file and I can install it after signing of course however the app fails to launch and I believe the reason is down to the warning I describe above. Am I missing any steps for packaging a net 5 application? I've taken the exact steps I have for a net framework application that have worked in the past.
So the app not loading was two fold. The app primarily didn't load as Entity Framework core 5 is referencing the wrong version of SQL Client. See https://github.com/dotnet/SqlClient/issues/652.
The second reason why the app wouldn't load was because the msix was trying to access a file I had open on another networked computer. See the section common problems https://learn.microsoft.com/en-us/windows/msix/packaging-tool/tool-known-issues.
Still no idea why the packaging project think it is net6 howwever.

"JBoss Tools Java Standard Tools AngularJS" will be ignored because it is already installed

Using JBoss Studio and importing sample jboss-forge-html5-archetype. When you click next; shows that plugin AngularJS Eclipse needs to be installed. When I try Download and Install it fails. It says it is already installed.
Has anyone seen this issue before? Where does JBoss Studio keep it's log files? Where does JBOss Studio list it's plugins? How do you un-install a plugin?
Thanks!
Log files are stored the same way as plain Eclipse does. Check in your ~/devstudio/ folder for .log files, or check your workspace's folder for a .log file. Or check the Error Log view while running Devstudio.
To list installed plugins / features, from within Devstudio,select Help > About. You can also uninstall features (not plugins) from that dialog.
If a feature needed by a quick start is already installed then you shouldn't need to reinstall it... But maybe you need to update it?
What version of Devstudio are you running? Which OS & version? Which JDK vendor & version?

Nuget Update is not working propelry

I want to update the Nuget packages used in the solution file and currently, I am using the following command to update the Nuget packages.
NuGet restore <projectPath> [options]
Reference: https://learn.microsoft.com/en-us/nuget/tools/nuget-exe-cli-reference#restore
If no solution file, packages.config, or project.json is found, NuGet gives an error.
Reference: https://learn.microsoft.com/en-us/nuget/tools/nuget-exe-cli-reference#remarks
But the problem is I am using the packages.ProjectName.Config instead of packages.config file.So the NuGet update is not properly working.
Note: Similarly if the folder contains multiple project and solution files the NuGet update is not working.
Please suggest how to overcome this issue?
Edit:
Initially I thought the packages.[projectname].config usage in my source is the reason for NuGet packages restoring but later I found that NuGet packages are not even properly restored with packages.config files.
I have more than solution and project file in my source, After deleting the other projects, The NuGet restore is working properly in my source.
Is having more than one solution file is the reason for Nuget not updating? Anyone faced the problems , Any help to overcome this issue will be useful.
Nuget restore requires a Visual Studio solution file, a packages.config file or a project.json file.
See the remarks for it's beavior.
Looks like you can't specify an arbitrary name but you should be able to accommodate your scenario as of NuGet 2.8. The project names just need to match the filenames - I don't imagine spaces are allowed.
NuGet release notes;
Individual packages.config Files for Different Platforms
When developing applications for multiple target platforms, it is common to have different project files for each of the respective build environments. It is also common to consume different NuGet packages in different project files, as packages have varying levels of support for different platforms. NuGet 2.8 provides improved support for this scenario by creating different packages.config files for different platform-specific project files.
Looks like ReactiveUI do this, so worth checking their repo;
ReactiveUI Github

Resources