I am having lots of issues trying to convert my output from gem5 simulator into a proper xml format for input to McPAT. I am using gem5 version 2.0 which is the latest version, and I am using the 2015 McPAT release. I was given a template.xml file from someone who had a McPAT environment working in 2010 version, however, the stats and config files in gem5 have changed format. Thus, I need assistance in finding a proper template.xml that works in 2018 for the latest versions of gem5 and McPAT.
https://github.com/Ayymoose/gem5-mcpat-parser
This repo on github showed me exactly what I needed to do its all in the README.
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 read the manual available here https://cwiki.apache.org/confluence/display/FLEX/Apache+Flex+SDK+Mavenizer. But it's confusing me. It's told that I should apply converter seprately to Flex SDK and Air SDK. But at present both of SDKs downloaded and merged by current Apache Flex Installer (should I download packages manually?). Also I don't have the flex-sdk-converter-1.0.jar. After build the mavenizer I have air-converter-1.0.0-SNAPSHOT.jar, flex-converter-1.0.0-SNAPSHOT.jar, base-converter-1.0.0-SNAPSHOT.jar and flash-converter-1.0.0-SNAPSHOT.jar.
How to use those tools to properly put Flex and Air SDK to the maven repositoy?
I also faced the same problem 2 months back.
The documentation on the website was for older version.
It has been updated on November 03rd.
Can you try again by following that?
This appears to be the current documented process now.
https://cwiki.apache.org/confluence/display/FLEX/Preparing+FDKs+for+Maven+builds
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.
We are working on a .NET application and recently started using Git for version control.
Our latest release was tagged in Git, and now i am trying to debug some issue.
Here's what i did:
Installed the app (from the release) on my Pc.
Checked out the tagged release version.
Started VS and attached to the process.
Placed breakpoints over some part of the code.
I am getting the message: "Source code is different from original version", however this is the actual code that was compiled to release this installed version.
What am i doing wrong here?
using VS2008 if that matters.
BTW: What is the mechanism that is used to compare if the binaries are different from source code?
When cloning the repo from Git, for example, it will change all files/folders date to the current date. Is this value (datetime) used to determine source code vs. binary?
The problem was i didnt use (or store) the original symbols for this release.
I previously thought symbols only contained source code line information and were not needed to actually debug the program under VS. apparently i was wrong.
A good resource on symbols for anyone who's looking into problems with them: http://www.wintellect.com/CS/blogs/jrobbins/archive/2009/05/11/pdb-files-what-every-developer-must-know.aspx
This post also contains a few other links to MSDN Magazine with more valuable information.
I have used jmeter 2.5 and ANT 1.8.2 and jdk 1.6. Also, I have used latest .xsl file path in build.xml.
Issue is iam getting NaN value for Min, Max in html reports.
Please let me know any solutions.
This problem is encountered in newer versions of Java.
I faced the same problem and this solution worked for me - Copy xalan-2.7.1.jar and serializer-2.7.1.jar from the apache-jmeter/lib folder and include it in apache-ant/lib folder of ant.
Somehow it's a problem related to newer Java versions: If you use Java 1.5 or higher it wont work out of the box, unless you:
Use the build file: http://svn.apache.org/repos/asf/jmeter/trunk/extras/build.xml
Include xalan.jar and serializer.jar both in jmeter lib directory
There are two bugs in apache bugzilla regarding this issue. More info:
http://vishnuagrawal.blogspot.com/2009/04/jmeter-run-tests-using-ant.html
http://jmeter.512774.n5.nabble.com/Min-and-Max-times-are-returning-NaN-td525870.html
Given it works in XP and not windows 7, try running in either:
As Administrator
Compatibility mode