I want to know what is the good IDE for running protractor files (.ts) files? I was using webstrom and it worked very well for me. Since my client wants to use visual studio with typescript, i have moved to that but could not able to run .ts files.
I have followed below steps:
installed tnode js tools for vs 2013
install typescript 1.7 for vs 2013
create a new solution ->typescript -> html application with typescript
installed jasmine definetely typed,angular-protractor defintely typed,selenium-webdriver.d.ts,node.d.ts
added the reference path and import to conf file
When i build and run, no build errors but it goes to localhost and not the url which i have specified in config file.how to resolve this? is it good idea to use visual studio or not?
Related
When I starts a new project (Blank App (C++/WinRT)) on Windows10 1909 # VS2019(up to date) its shows up a lot of errors as if the extension wasn't installed. But after trying to compile and run its works - so why do I get the errors and how can I solve this? screenshot
Edit: I have fond a solution for that. its turns out that the project was needed an additional include directory:
under the project properties->C/C++->General->[Additional Include Directory]
I added the winRT folder:
C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\cppwinrt
screenshot2
and that's it now there's no errors (correction - after creating new project its still have the same errors)
edit2:
Update: I installed the last windows 10 SDK and was still getting the seam errors. Than I installed a package via cmd with the following command:
D:\vcpkg> vcpkg install cppwinrt:x86-windows
after this was done it seem to work now
edit3:
I'm sorry for the annoying newcomer questions...
its looks like I have another problem now with my project
in the packages.config file is says that the package is not declared with the following warning packages.config pic
thanks for any help in advance.
(edit4) I followed this thread:
nuget 'packages' element is not declared warning
and that's it, now all I have to do is to learn how to code :D
The 'standard' include paths for Visual C++ projects are the VC_IncludePath and WindowsSDK_IncludePath. The Windows SDK includes path already has all of the directories:
include\<10.0.build.0>\ucrt
include\<10.0.build.0>\shared
include\<10.0.build.0>\um
include\<10.0.build.0>\winrt
include\<10.0.build.0>\cppwinrt
"Blank App (C++/WinRT)" is not part of the standard VS 2019 template set. The name of the project in the screenshoot is "ConsoleApplication2", which would imply you created a Win32 console C++ project instead of a C++/WinRT project. Even still, you can reach the standard C++/WinRT headers from a Win32 console application since they are part of the standard path.
From the looks of the errors in your first screenshot, it appears you are using a generated C++/WinRT rather than the one in the Windows 10 SDK. With VS 2019, you must add the NuGet package Microsoft.Windows.CppWinRT to your project to get the MSBuild rules needed to build with the C++/WinRT VSIX installed, so that's likely a problem here. See VS Marketplace
I'm trying to run ESLint on Visual Studio 2019. It works fine until I add eslint-plugin-prettier in my package.json. Then I get this error.
internal-error | (ESLint) Failed to load plugin prettier: Cannot find module 'eslint-plugin-prettier'
If I open the command prompt I can run eslint and it has no trouble finding the prettier plugin.
My next step is to go into the ESLint source code, find that error, and figure out where it's looking for "eslint-plugin-prettier". But I can't figure out what copy of ESLint Visual Studio is running. It works even if I uninstall ESLint both locally and globally, so I guess it's running an internal copy?
Is there a way to find out for sure what copy of ESLint Visual Studio is running?
I also wanted to find this information, and here is what I did:
Go to C:\Users\\{YourWindowsUsername}\AppData\Local\Microsoft\TypeScript\ESLint.
Open the package.json file.
You should see the version of ESLint that is installed, in my case it is "eslint": "4.19.1" for example.
Zend Studio 10.6.1 on Windows 8.1:
How to run PHPUnit Selenium inside Zend Studio (Version 10.6.1)?
Zend Studio 10.6.1 has a built-in version of PHPUnit 3.7, but no phpunit-selenium package installed.
I tried installing phpunit-selenium in my PHP project, without success.
installed as a phar archive (phpunit.phar downloaded from phpunit website).
installed with composer in my PHP project (require: phpunit-selenium >= 1.3.3).
unpacked the phar archive and including it in my project.
installed a complete current PHPUnit package (Version 4.1) in my project.
The effects were that either the PHPUnit Selenium classes could not be found, or that the tests would not run, or that PHPUnit didn't run at all anymore from within Zend Studio.
I'll answer this question by describing how I worked around it to get it to work finally.
A clean solution would be to edit composer.json in the built-in PHPUnit of Zend Studio.
The path to the built-in PHPUnit of Zend Studio under Windows is:
c:\Program Files (x86)\Zend\Zend Studio 10.6.1\plugins\com.zend.php.phpunit_10.6.1.v20140329-2132\resources\vendor\phpunit\phpunit
and / or:
c:\Program Files (x86)\Zend\Zend Studio 10.6.1\plugins\com.zend.php.phpunit_10.6.1.v20140329-2132\resources\vendor\phpunit\phpunit.org
There seem to be two identical versions.
However, after some dabbling around with composer, I couldn't manage to resolve the error messages, and gave up on it. I hope this can be solved in the future because it would be the cleaner solution.
Here is a successful Workaround:
install phpunit-selenium via composer in project;
copy the files over to the built-in PHPUnit of Zend Studio;
edit the file vendor\composer\autoload_classmap.php under the project directory:
find the lines that start with 'PHPUnit_Extensions_Selenium' and copy them to clipboard;
edit the file c:\Program Files (x86)\Zend\Zend Studio 10.6.1\plugins\com.zend.php.phpunit_10.6.1.v20140329-2132\resources\vendor\composer\autoload_classmap.php:
paste in the copied lines that start with 'PHPUnit_Extensions_Selenium';
remove phpunit-selenium from composer in project and from project;
I have this simple test project in vs 2013 I reference the Microsoft.TeamFoundation.Client in my library so added a Microsoft.Teamfoundation.Client.12.0.0.0.Fakes in the test project, using right click add fakes assembly.
Locally everything works fine but when i run the project trough the build server using the default template I get Fakes: code : assembly XXX\Microsoft.TeamFoundation.Client.dll failed to load properly.
The non fake dll's are included in a solution folder.
Any other assembly added by fakes working perfectly fine but as soon as I fake the Microsoft.Teamfoundation. my build breaks.
Using VS2013 with TFS 2012 update 2.
I had the similar issue. The problem is because TFS and Visual Studio versions are not the same. I installed VS 2013 to the server where TFS Build Server installed.
Then renamed C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\Fakes folder and copied
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\Fakes folder into C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\Fakes. This will solve your problem I guess.
I have made an application using Qt 5.0.2 and made its build using inno setup. The application is successfully installed and launched at my system and worked fine.But when i installed it on other system, application is not installing or launching also no error showing. Please help me guys... What to do
If you are using visual studio to build your application you will probably need to install vcredist_sp1_x86.exe on the destination machine. You can find it somewhere in the installation folder of Qt. You can add it to the list of files in the Inno script, and add entry in the [Run] section. Also make sure you have included in your setup script:
Qt5Core.dll
Qt5Gui.dll
Qt5Widgets.dll
libGLESv2.dll
icuuc49.dll
icuin49.dll
icudt49.dll
D3DCompiler_43.dll
plugins/platforms/qwindows.dll ->should be installed in platforms/qwindows.dll in the destination folder. The same applies to imageformats plugins if you use them.
If you think there are too much dlls you will need to rebuild Qt with other configuration options, but that's another story...