I am learning C# and trying to develop a git client, currently using the library: libgit2sharp,
Now I have a requirement to display and support modification of git global config, such as "user.name" or "user.email".
bug I did not find the corresponding documentation in the official wiki
One more question, I am running the program on a Windows Arm64 device and libgit2sharp doesn't seem to support it, is that true?
Windows Arm64 Error Image:
enter image description here
Related
We are building Xamarin.Android projects on TFS (on-premise).
With every Visual Studio / Android SDK update we have to update all our build agents.
Is there a way to simplify this process?
There are some vsts-agent images available, but none of them are for xamarin. There are some xamarin-related images, but they are a bit out of date (and not related to TFS).
Is there anything I'm missing? Any other solutions to the problem?
Currently, there are no Docker images support for xamarin or windows. Even for the existing Docker images, there are not for all TFS versions. As you can see from vsts-agent images:
Ubuntu 14.04 and 16.04 are the currently supported OSes, but there are
plans for Windows support.
When used with VSTS, the agent version is automatically determined and
downloaded at container startup based on the account to which the
agent is connecting. When used with TFS, an image that matches the
installed TFS version should be chosen.
There are no better way to do that. So, you have to update the build agents manually once there are any SDK updates.
You can also submit a User Voice to suggest the feature on this site: https://visualstudio.uservoice.com/forums/330519-team-services
Actually a similar user voice submitted here,
Another workaround is migrating to VSTS (Visual Studio Team Services ) and using the hosts agent (Generally the hosts anget will be updated accordingly once new SDK/components updated, See this user voice).
I am trying to add our first Azure Function App, which will read from a queue and update an Azure Search Index. I wrote everything in a C# dialog app to make sure the data would parse and upload properly.
Apparently when you are running in Azure the following line of code is too much to ask for:
using Microsoft.Azure.Search;
Azure has no idea what that library is, and now I have to stop using the Portal and download Visual Studio 2017 and follow a long list of steps to put this Microsoft supplied reference into my Azure bin folder for Azure Functions?
Really Microsoft? I just need access to the Search objects and I am done, but the little documentation I can find says I need to spend a few days installing software and setting up FTP somewhere if I want to get there.
Is there a more direct path?
If you develop function through the portal then use NuGet package. The package is called Microsoft.Azure.Search
In short, you have to create a project.json file with the required NuGet package references.
Here is a good explanation and here you can find Microsoft documentation.
I have been working on .net platform for few years now and I must say I am very impressed by how Microsoft is making .net cross-platform compatible.
I spent hours trying to run a small hello world application built using CoreCLR on a mac. And it worked. While There are still a lot of UNKNOWNS I am still trying to understand, there is this one question I was not able to find answer of on google.
How do you automate the deployment a dnx application. I mean, do you compile your aspnet 5 app into a nuget package and then restore it on your linux server (I have never used linux so not sure how nuget works there), and run dnx command ? Or just zip it and push it to the server directly ?
Sorry this is all very new to me and so my questions might sound stupid. I just want to know what's the best way I can implement continuous delivery for my asp.net 5 applications. My ultimate goal is to host my apps on linux containers.
You can use dnu publish --runtime <name of runtime> --no-source. That creates a folder that has your application, its dependencies, and the runtime. Then, all you have to do is get that folder on your server.
How you move files around really depends on your scenario... It could be FTP, Storage, Kudu (if you're on Azure WebSites), etc.
Another alternative is to do the restore on the server. While this reduces the size of the application when you publish, you will have to restore packages on the server which can be insecure and it can also lead to application breaks because there might be newer, incompatible packages on the feeds.
While there's no right answer to fit all, I found that if you want to most reliable and consistent results, you should publish with everything, test locally and then just copy the bundle on your server.
For docker, I recommend the same thing. Publish with runtime and no sources and create a container that has the resulting folder.
Is there a ways to rebuild a c# .net CF application and deploy it in windows mobile emulator from the command-line?
This is required to create a bat file for automation.
I have taken a look at http://msdn.microsoft.com/en-us/library/aa188169(VS.90).aspx which mentions how to use the emulator from command line, but doesn't mention how to deploy an application in it.
Thanks,
Vicky
I just tried calling devenv with the /deploy switch to tell it to deploy to the target and it worked just fine:
devenv /deploy Release "MySolutionName.sln"
There are two steps involved:
Start the emulator using the Device Emulator Manager (DEM) API
Execute the target app remotely using RAPI or RAPI2
1. Start the emulator using the Device Emulator Manager API
To programmatically start your emulator you'll need to utilize the Device Emulator Manager (DEM) COM API. To do so from .NET, you'll want to use the Microsoft.DeviceEmulatorManager.Interop.9.0.dll Primary Interop Assembly, which should be found here (assuming your OS is 64 bit): C:\Program Files (x86)\Microsoft Device Emulator\1.0
While you can use the provided PIA directly, it's much easier to access the DEM API from a custom façade; fortunately, a nice wrapper has already been written and is available from MSDN, along with some great info regarding the API:
How To: Programmatically Control the Windows Mobile Device Emulators from .NET - MSDN
Note: You must "dock" the emulated device before you can use the Remote API - don't forget this step!
DEM documentation:
Device Emulator Configuration Files - MSDN
Device Emulator Manager - MSDN
2. Execute the target app remotely using RAPI or RAPI2
Once you've guaranteed that your emulator is both running and "docked", you can proceed to interact with it via the Remote API (RAPI), allowing you to upload your compiled executable to the device and execute it remotely. Here are a few examples of RAPI use:
Communicating with a Device from the Desktop (C#)
The RAPI Demo Example (C++)
Simple CE synchronisation utility with Python features (IronPython).
A demo of the Windows CE Remote API (IronPython)
RAPI Documentation:
Remote API (RAPI) - MSDN
Remote API 2 (RAPI2) - MSDN
Conclusion
This should give you everything you need to piece together a simple CLI app to programmatically launch a given app on a given emulator. Please leave a comment if you have any questions.
For deployment to the emulator from the command line, see http://sevaa.home.sprynet.com/cedeploy/
I want to create a windows mobile app (windows mobile 5.0 and above, using CompactFramework [in SharpDevelop]) to capture photos automatically, without user involvement (like it would be with CameraCaptureDialog). After going through google searches I found out a solution that should work (http://blogs.msdn.com/marcpe/archive/2006/03/03/542941.aspx)1 but I cannot compile the source (I guess that is because I use sharpdevelop not MS Visual Studio).
Are there any other options available?
Maybe there is a binary version of that CameraCapture Library somewhere so I can use it without compiling on my own?
Anyone willing to compile the one I linked above and post it somewhere to make binary version available [I tried searching for such in google, but with no success]
The CameraCaptureDialog is part of the Microsoft.WindowsMobile.Forms assembly, which chips in ROM on WinMo 5.0 and later devices. The device SDKs also whip with copies of these assemblies so the apps can build (for example mine is on my PC at C:\Program Files\Windows Mobile 5.0 SDK R2\Managed Libraries). I would assume you should be able to manually add a reference to that assembly in SharpDevelop.