I had an opencpu application packaged in R, and installed locally and used by opencpu$browse(). It's been a while since I used this and after updating opencpu to the latest version, it doesn't recognise this function anymore and I can't find release notes referring to any changes. Has the opencpu design changed so that I have to have my package on github now or is there an alternative function I should use now?
OpenCPU 2.0 was released yesterday and the single-user server has changed bit. To start an app and open it you now need to use ocpu_start_app("user/repo") for example:
ocpu_start_app("rwebapps/nabel")
Or to open a locally installed app:
devtools::install_github("rwebapps/nabel")
ocpu_start_app("nabel")
The manual page ?ocpu_start_server has more examples and details.
Related
Is there a way to give users a link to the latest version of Windows Terminal msixbundle?
Or even how to get the URL programmatically?
Like pseudo code:
location=curl -sI https://github.com/microsoft/terminal/releases/latest | grep location:
version := path.Base(location)
versionNoV := version[1:]
wtfisthis := "8wekyb3d8bbwe"
base_url = "https://github.com/microsoft/terminal/releases/download"
url = fmt.Sprintf("%s/%s/Microsoft.WindowsTerminal_%s_%s.msixbundle",
base_url, version, versionNoV, wtfisthis)
GitHub doesn't provide an automatic link for the latest release that can be used to directly download a release asset. In general, you should be careful about trying to do this, since sometimes the latest release is a new major version, bringing in incompatible changes.
However, you can query the GitHub REST API to find assets related to the latest release. That will contain the proper URLs to use. However, it is not static.
Normally, this is possible for GitHub releases if the released binary has a static filename.
So, for other projects you can simply download the latest release with a fixed URL like: https://github.com/ytdl-org/youtube-dl/releases/latest/download/youtube-dl.exe. Unfortunately, that will not work with the current release process for Windows Terminal.
Reference: https://docs.github.com/en/repositories/releasing-projects-on-github/linking-to-releases
Several people have contributed short scripts to help address this here: https://gist.github.com/steinwaywhw/a4cd19cda655b8249d908261a62687f8
I have an application that works on a previous version of the WAMP stack.
There are couple of changes in Apache, which were not relevant when the application was on that stack, but now are. This also prevents the application to run on the current stack.
To get it working, I need the older version of WAMP stack. Any way I can download that? Or a suggested path to upgrade to newer versions of the WAMP stack?
Thanks
You can search for it in archive.org.
The file has the same url but it's not linked in the description page.
For example, now I need the dmg file of the version 3.0 of redmine, so I go to: https://web.archive.org/web/*/https://bitnami.com/stack/redmine/installer
And copy the url from the download link from a date prior to the launch of the 3.1 version.
Bitnami developer here. You can request the version of the stack that you want in the community forum of Bitnami. You have to create a new post and tell the stack and the version that you want. https://community.bitnami.com
I hope it helps.
I'm trying to follow the directions to setup olingo-odata4-js on a windows 8 machine.
http://olingo.apache.org/doc/javascript/project-setup.html
First Problem
After installing the main modules navigate into the folder /grunt- config/browserify_transforms/stripheader and call again npm install
But there is no such directory anywhere in the cloned repo.
Second Problem
When I open up the solution in Visual Studio, the gnuget package manager asked to restore the packages. However, the following error occurs: "unable to find version 6.0.0-beta1 of package Microsoft.Odata.Service"
Anyone successfully go through the setup? Everything looks clean and well written. I'm sure I'm just missing something.
it is a bit long story about the missing Microsoft.OData.Service 6.x, it does exist but is not officially released to public. unlike Its previous version that is for odata V3 protocol, 6.x library is for odata V4 protocol, since Microsoft OData team decided to move away from WCF Data service, and instead wanted to recommend RESTier for OData V4, so 6.x's service dll was not released.
that is why Apache Olingo doesn't make it public either. but if you need, we can provide private bits to you for running olingo-js tests (as a temp solution).
I downloaded the latest adt bundle (adt-bundle-windows-x86_64-20140624), and uncompresed that zip file, but when i try to open that adt, it open as juno eclipse. can any body help me to resolve this prblem.
thanks in advance
ADT Bundle contains Eclipse, to start Android development you need the ADT and the bundle comes with both you don't have to spend time searching for the ADT and Eclipse
Same problem here, using OSX. The downloaded ADB dows not show the typical ADB buttons and other extension provided by the plugins, but just a plain Eclipse. Installing an older version of ADT (adt-bundle-mac-x86_64-20140321) and updating won't help.
The package seemes somehow broken, some files like the ADT app icon, just aren't there. Other people experimented problems (Same problem; Other problem, also documented here).
I know it's not a real answer, but I just switched to Android Studio. I think the only other option is reverting to an older versione and wait for a new release.
To not get blocked I've continued to install the latest ADT Bundle 23.0.0 and adt-bundle-windows-x86_64-20140624 fresh on my system. Updated the SDK to the latest and continued to set "targetVersion as '19'" instead of setting it to 20 or 21.
That way you can proceed ahead with your coding and later when things get resolved...you can implement that to new version. BTW, I've also selected 'Blank Activity / Empty Activity" during the project creation
Comment back if it makes sense or NOT until the problem gets resolved by Google... :)
The Bug thread about this issue can be tracked here : Latest ADT Bundle Bug Tracker
I'm trying to use the latest Exchange Web Services DLL, however when I search my hard drive I see many versions of Microsoft.Exchange.WebServices.DLL, the most recent being version 14.0.650.7 with a date of 1/24/12.
I want to rebuild my machine but can't find an official place to get this DLL. I attempted to download the latest SDK I don't see any DLL to use, nor is there any CHM for me to use.
Where can I get the latest version of Microsoft.Exchange.WebServices.DLL?
Current version of the EWS Managed API is 1.2. It seems that Microsoft sometimes forgets to update links to the newest download which makes it hard to find out what the newest version is but I usually go to www.microsoft.com/downloads and search for "Exchange Web Services Managed API" whenever I need a fresh download.
UPDATE:
EWS is on NuGet:
http://www.nuget.org/packages?q=EWS
This is an old question, and the two answers by the OP and #JakobChristensen do answer the question. I'll just mention that I'm finding the situation fairly confusing.
I recently (manually, not via NuGet) downloaded the current NuGet version, which they currently call "2.2.0".
https://www.nuget.org/packages/Microsoft.Exchange.WebServices/
But the internal file/product version on the .dll is 15.00.0913.015.
According to this page
https://msdn.microsoft.com/en-us/library/office/dn528373(v=exchg.150).aspx
the file should be placed here:
C:\Program Files\Microsoft\Exchange\Web Services\2.0\
So that's where I placed it. Later, when playing around with a Microsoft sample program I noted that it did indeed reference the file at that location.
But another Microsoft sample program referenced the file in the GAC!
C:\WINDOWS\assembly\GAC_MSIL\Microsoft.Exchange.WebServices\15.0.0.0__31bf3856ad364e35\Microsoft.Exchange.WebServices.dll
This version had file/product version 15.00.0847.030.
I'm not sure how that file got there, probably part of a Visual Studio installation.
There's also something called EWSCore, which is apparently a forked version of the official EWS with some bug fixes.
https://www.nuget.org/packages/EWSCore/
My current decision is that I'll consider the official NuGet version to be the version I'll standardize on, and manually download it to my development PC and my build PC and place it here:
C:\Program Files\Microsoft\Exchange\Web Services\2.0\
Options
If you use .net framework, there is a nuget package "Microsoft.Exchange.WebServices 2.2.0" here https://www.nuget.org/packages/Microsoft.Exchange.WebServices
If you use .netstandard/.net5+, you need to go the Github open source project "OfficeDev /
ews-managed-api" here https://github.com/OfficeDev/ews-managed-api , and there you download the code, and compile it. However, this project is targeting .net3.5. So, you need to convert/upgrade it to .netstandard/.net5+ manually and compile it for your self.
!! Update !!: I took the version as of date of this post from GitHub. Replaced Old Style project with SDK project. Target framework set to netstandard2.0. Added packages System.DirectoryServicesandSystem.Security.Cryptography.Xml. In files, I had to remove few namespaces that not compatible, but were not used. Removed AsImageinPhoto, this is public image retrieving method, not needed - it only converts byte array. And fixed loading issue with Assembly.GetExecutingAssembly().GetTypes();`
Type[] types;
try
{
types = Assembly.GetExecutingAssembly().GetTypes();
}
catch (ReflectionTypeLoadException ex)
{
types = ex.Types.Where(t => t != null).ToArray();
}
I also deleted or excluded from project bunch of files related to documentation, fxcop, and assembly info.
And then it worked for sending emails with different API versions. Reading emails is not tested yet.
There is a third option. Nuget has a package "Microsoft.Exchange.WebServices.NETStandard 2.0.0-beta3" But this is not an official Microsoft code. https://www.nuget.org/packages/Microsoft.Exchange.WebServices.NETStandard/2.0.0-beta3
!! Update !!: Got this version and compared to the original code in option #2. This code has more changes than necessary to convert to .netstandard. It has some async stuff added.