After 4 days searching intensely about why my Visual Studio is not recognizing the ionic html tags and AngularJS parameters, I came here to find the answer and can help others too.
Installed Visual Studio Community 2015 - Update 3
Installed Apache Cordova tools for Visual Studio
Installed Node.js 64 Bits (v6.3.1)
Installed Ionic on npm: "npm install -g cordova ionic"
Created a Ionic project on console: "ionic start myProjectName"
Converted in a Visual Studio Solution (Project from existing code).
First build downloaded rest of the things.
Opened a ionic html and:
Project structure:
P.S: I don't use Resharper, and I installed the Ionic Pack from Extensions and nothing happened.
ANSWER FOUND
Worked for me:
Delete the Visual Studio folder from app data
C:\Users\ (yourusername)\AppData\Roaming\Visual Studio
This will reset your Visual Studio style, configs and caches.
Related
I've got a solution in MS Visual Studio with ASP Net Core Web API project.
I want to add standalone React JS project to this solution.
NPM creates folder with project in \AppData\Local\Temp\ folder but cannot copy it to the folder where my solution is with error:
Couldn't find a part of the path.
If I run npm start in temp folder, it starts fine server and shows default page.
How can it be solved?
I use Microsoft Visual Studio Community 2022 (64-bit) - Current
Version 17.2.0
I am new to mean based app development .I am following the here to configure the app i have installed all the prerequisites as mentioned in the link but getting error while executing the working on windows 7
npm install -g mean-cli
Error
I have installed and updated the Visual Studio C++ template which got the issue fixed
My intellisense is not working in visual studio 2015.
I have a _references.js file under the scripts directory that points to all my angular files.
I have angular.intellisense.js in my options set up under Implicit (Web)
My project is a MVC/WebAPI project created in Visual Studio 2013.
Could this be the issue because I didn't create the project in VS2015?
My angular structure.
-app
--admin
--components (all angular and js files for site go here)
--core
--dashboard
First of all, I am very beginner in using node.js / angualar.js /protractor.js and jasmine.js stuff and I am not from web dev corner at all.
But for now, I just want to create some protractor test for an angular app and this is actually working quite fine. But I am wondering if it's possible to get VS2013 intellisense working?
I would really appreciate if VS would suggest functions of objects like 'browser.xxx'.
I am really stuck with that, looking forward for some hints!
thx Florian
Ill just give an answer to myself! To get Visual Studio 2013 intellisense and debugging working for angular protractor tests, follow these steps:
Install node.js
Install protractor (global) („npm install -g protractor“; „webdriver-manager update“)
Install Visual Studio 2013 node.js Tools
Install Visual Studio 2013 TypeScript Tools
Create a new project „Typescript\Node.js\Blank Node.js Console Application“
Add your „conf.ts“ and „spec.ts“ files to the project
Right click on „conf.ts“ and select „Set as node.js startup file“
In „Project properties“ set your „Node.exe path“ to your protractor executeable file, eg. „C:\Users\myUser\AppData\Roaming\npm\protractor.cmd“
Download typescript DefinitelyTyped definitions from git hub:
https://github.com/borisyankov/DefinitelyTyped
In your VS2013 project folder „Scripts\Typing“ create the subfolders „jasmine“, „protractor“ and „selenium-webdriver“
Add the typing definition files "angular-protractor\angular-protractor.d.ts", "jasmine\jasmine.d.ts" and "selenium-webdriver\selenium-webdriver.d.ts" into the appropriate project folders you created in the step above.
Write your protractor test and enjoy code highlighting
Start webdriver-manger „webdriver-manager start“
Hit „F5“ to start debugging
Enjoy!
Florian
I have a client with dnn website. I need to develop module for it. How I can start? I'm using Microsoft Visual Studio 2010 now (trial version). I cannot access source code, just make new module and install it. What is the best practice to start on the environment like this? Other question is if I using trial version of visual studio, is my module will expire too?
These materials, especially video tutorials, might be really helpful to you when getting started with DNN module development: http://www.dotnetnuke.com/Resources/Wiki/Page/Module-Development.aspx They cover every part from installing DNN module project templates to development and packaging of the custom DNN module.
To your second question, the answer is no, your module will not expire after VS2010 trial expires. Another option for you is to use free express editions of visual studio 2010, for this case Visual Web Developer 2010. You can download it here: http://www.microsoft.com/visualstudio/en-us/products/2010-editions/visual-web-developer-express You will not be able to use source control directly from express edition, but still there is option to use SVN and a client like TortoiseSVN.
Purchase and read this book: Professional DotNetNuke Module Programming
Visit the download page of DotNetNuke.com
Download the Community Edition. Install it on your dev machine, get it working.
Hook the Desktop Modules folder and bin folder (at least) to your source control
At the download page above, install the Visual Studio Starter Kit
Restart Visual Studio 2010
Start up Visual Studio 2010, create a new compiled DNN module project, make sure its location is in the Desktop Modules folder of DNN
Implement some test code
Install the module on DNN (install by manifest)
Add the module to a DNN page. Test it.
Make updates to your DNN module. You only need to uninstall and reinstall the module if you add or remove files or change the database setup scripts.
Build a deployable version of your module. (You make a zip file or something. Just read the book. I always have to refer back for this step)
Practice installing the DNN module on another fresh DNN Community Installation.
Once you are satisfied that it is installing correctly, install the module on the live site (Do backups first, just in case)