I would like to move my test cases from an older system into the TFS system. I discovered the "Test Case Migrator Plus" tool, however after downloading & extracting zip file, I cannot find the TestCaseMigratorPlus.exe file. Project info can be found at: https://archive.codeplex.com/?p=tcmimport
Does anyone have suggestions on getting the the .exe file so I can begin the migration process? Are there other tools available to do this task? My test case data is in both cvs & xls format.
Looks like the archive zip file contains all the releases. But they're named a bit weird. Looking at the releases manifest you should be able to just rename this file releases\0\427b6077-824e-48ef-8eed-8111cc2f7fbc to TestCaseMigratorPlus(Excel-MHT) V1.1 RTM Binaries.zip:
{
"Id": "427b6077-824e-48ef-8eed-8111cc2f7fbc",
"FileName": "TestCaseMigratorPlus(Excel-MHT) V1.1 RTM Binaries.zip",
"Url": "./0/427b6077-824e-48ef-8eed-8111cc2f7fbc",
"Type": "Application",
"UploadDate": "2012-01-02T00:15:57.42-08:00"
},
Related
I am trying to publish my electron app to Windows store but it is showing default electron icon whereas the exe created has correct icon. Even on launching the Appx file, correct icon is showing up. How can I change the default icon of electron and put the correct icon on store?
Package JSON:
"build": {
"appId": "xxxx.xxxx.xxxx",
"directories": {
"buildResources": "build"
},
"win": {
"icon": "assets/icons/win/icon.ico",
"target": [
"Appx",
"nsis"
]
},
"nsis": {
"artifactName": "${productName}_Setup_${version}.${ext}",
"installerIcon": "assets/icons/win/icon.ico"
}
Add a folder as a sub folder under build. build->appx(must be appx)
Then add some icons named as Square44x44Logo.png, Square150x150Logo.png, StoreLogo.png, Wide310x150Logo.png
I believe you can get the image resolution from the name. for StoreLogo.png 256*256 will be fine.
As tpikachu pointed out, you haven't correctly defined the graphical assets form your package. Doing this manually is quite tedious and error-prone.
Tools like Advanced Installer Express (free forever) handle such configurations automatically. Here is an article about how to package an MSIX for an Electron app with Advanced Installer, and another one about how to publish your app in the MS store:
p.s. I work on the team building Advanced Installer
Today having problems with the Excel file on a Windows 7 laptop. I worked with this file last night without any problems.
The file was saved on a network drive and during saving have not been received error.
When this morning I needed to open the file I got the message about error.
"excel cannot open the file because the file format or file extension is not valid" And also the file is showing up as having 0kb.
Tried an excel repair on the file and also opening up in another program like .docx or .txt. Is there any way of finding out what happened this file or fixing the issue.
File server is running windows 2012 R2 server. Shadow copies are available and I can restore the file to previous version, however the user did alot of work after that time.
I think your file is corrupted and it may be repaired using an excel repair tool; I personally have not used the Excel version of this maker but I have used the Excel Repair Kit and password tool and they work well:
However, if the user was working for a long time Excel may have saved a copy in the users computer C:\Documents And Settings\UserName\Application Data\Microsoft\Excel\filename.xlsx.
Another thing, I use Undelete Server Edition and it has worked great for the last 5 years; every time a user saves a file it makes a copy and it stores it for the time you specify.
How I do to work with non-Core Asp.Net MVC projects on Visual Studio Code?
I'm tired of slowness of Visual Studio Community, so I was thinking about if I can setup an VS Code environment for that.
Here is how I was able to do it for my projects:
Install Visual Studio Code (obviously)
Install C# plug-in (I hope you are using C#) - main benefit here is intellisense, syntax highlighting, some refactoring options
Make sure you have msbuild in your environment path for building solutions
Now the basic flow looks like this:
Open Visual Studio Code
Choose File -> Open Folder... menu option and open the folder that contains your asp.net mvc solution
CTRL+SHIFT+P to run VS code command and find "OmniSharp: Select Project"
Choose your solution
Wait for OmniSharp to load (you can inspect its output by bringing up output view CTRL+j, select Output, 'OmniSharp Logs')
At this point you should be able to Go to any type with CTRL+T and typing the type name. Use CTRL+P to find files and edit them. And to build press CTRL+SHIFT+B. If you don't have vscode task configured for building, I believe VS Code will build a scaffold file for you which you need to fill out and then msbuild can be invoked to build your solution. Check mine out (put this in .vscode directory, in a file called tasks.json):
{
// See https://go.microsoft.com/fwlink/?LinkId=733558
// for the documentation about the tasks.json format
"version": "0.1.0",
"command": "msbuild",
"args": [
// Ask msbuild to generate full paths for file names.
"/property:GenerateFullPaths=true",
// "/p:Configuration=Release",
"YOUR SOLUTION FILENAME.sln"
],
"taskSelector": "/t:",
"showOutput": "silent",
"tasks": [
{
"taskName": "build",
// Show the output window only if unrecognized errors occur.
"showOutput": "silent",
// Use the standard MS compiler pattern to detect errors, warnings and infos
"problemMatcher": "$msCompile"
}
]
}
It will take some time to get used to but once you are there, it's awesome. No more VS.NET memory hogging and overall slowness.
I love it how fast the editor starts and closes. Just get used to the flow of open folder, CTRL+T or CTRL+P for navigating between classes/code files. And be patient with OmniSharp (C# plugin) as at times it becomes nonresponsive and syntax highlighting becomes unavailable. At that point, I just restart OmniSharp (via a CTRL+SHFT+P, find OmniSharp, restart option).
Biggest things I miss: debugging. VS Code with C# plugin only supports .NET Core debugging as far as I know. The way I get around this is usually having unit tests and then isolating the code I want to debug via a unit test and just iterate on the test until the problem is solved. In rare cases where I absolutely need a debugger, I just power up the good ol' Visual Studio beast, do debugging and get out.
Hope this helps!
I've successfully setup my Visual Studio 2015+ ASP.NET project on VSCode.
I've created an gulpfile that handle the build for me:
It starts an IISExpress instance.
Refresh my browser on razor code change.
And automatically rebuild my application when I change C# code.
You can find the gulpfile on my project's Github
EDIT
Like suggested in the answers, i submitted this behavior to visual studio, and as a solution, i removed those special characters in the files name.
Visual Studio Team Services (was TFS Online) generated a build of the new version of my the solution, no problems in that. But i noticed that some files that i uploaded that have some special characters (ã,ç,õ), were generated with other characters, like "ç" changed to +º+.
We can't upload files with those characters? Or is some configuration that i am missing in the build configurations or elsewhere? Or some files with wrong encoding ? I uploaded .mp4 files and those special characters were changed as well.
Searched for this particular problem and only found problems with file name too long.
Looks like a bug. You probably need to submit it on the UserVoice site:
https://visualstudio.uservoice.com/forums/121579-visual-studio-2015
I am challenged with creating an automated release for a legacy Delphi (Delphi 2006) project.
I am a complete Delphi noob. So my question is maybe heading in a wrong direction ...
As far as I understood the release process of the given project it works like this:
A developer opens the project in Delphi Studio
Right-Click on the Project -> Properties -> Version Info
He sets the new version number of the next release in the Dialog.
He saves the project. This automatically generates the corresponding .resx file which contains the version number in binary form.
The .bsproj and the the .resx are checked in into source control
The automated build (Hudson) picks up the change and builds the release.
I would like to automate this process, since there are several projects that needs to get a new version number for each release.
I guess I could easily manipulate the .bsproj with a custom tool since it is xml.
However I am struggling with the generation of the .resx file which is currently done when saving the project in Delphi Studio.
Is there a way to automate the generation of the .resx? i.e. with a commandline-tool or something similar?
Or is there a smarter approach?
Any help is appreciated.
You can do it all in a batch file
Update the version numbers as specified in this SO question: change version number at build time
Use the DCC command-line compiler to build all the projects. There's plenty of documentation for that, basically you do just dcc32 <project>.dpr
DCC is e.g. documented here or here
I do wonder where your .resx files come from, but they can be converted as well. See this SO post.
Give it a go using these resources and for specific issues write a new SO question with your attempts so far.