This is probably a silly question but i am having troubles programming in angularjs with visual studio whenever i separate the application to different files.
For example, if i include everything in the same file (index.html):
<script src="libs/angular.min.js"></script>
var app = angular.module('myApp', []);
Visual studio automatically understands what is the object angular and what functions in contains and whenevery i type "angular.", it opens a window with suggestions.
But when i separate everything to different files, for example: app.js, routing.js, controllers.js, etc...
The application still runs but since i include angularjs in one file and use it in a different file, visual studio doesn't "help" me anymore...
So yeah.. it's silly but it really helps me program, especially because i'm new to angularjs.
Is there a way to fix it?
Thanks,
Arik
NuGet
If you would like to add AngularJS intellisence to your project you should add the NuGet package by John Bledsoe. There is a full article here it explains how to add the package so you have the coding help you require.
File Structure
There is a great article here that shows you the best way to structure your AngularJS application. Its a great article and can help when handling larger AngularJS projects but should be used even for smaller apps.
Background
In our environment, we are constantly making changes to our work item types (WITs), due to changes in our procedures. We currently have two main collections; one collection has around 5 projects, and the other one has around 20. For each project, we have 7 different WITs.
It gets kind of cumbersome when I have to make the a change to the templates, because I have to change them on every project/collection that we have. Typically, I just modify one template, and use the command line (witadmin) to import that xml file into each project. It's really difficult to know whether or not WITs are current on all projects.
What I am looking for
I would like to find a way to easily modify the WITs once, and have
it update all of the projects with those changes.
It would also be nice to have a GUI to modify these WIT. Does TFS 2012 and TFS 2013 handle WIT modification better?
What I Already Know
I am pretty comfortable running TFS/DOS commands, so I ultimately could
create a batch script that would automate that for me. This would
probably be a last resort scenario.
Another option would be to write an app using the TFS SDK and import the WITs to all projects.
Current Configuration TFS 2010 and VS 2012 (We are soon upgrading to TFS 2012)
Fortunately Grant Holliday did an excellent post on that topic.
A quick method is automating your WIT export\import with batch files (ExportWITDs.cmd, ImportWITDs.cmd). Then use the Checkin.cmd example to check-in the changes to a dedicated folder for WITs on the source control.
If your'e looking for a tidier, more robust solution, go for the TFS-SDK. A Visual Studio extension that adds an Export\Import\Sync All WITs buttons would be great.
Here's a problem which is driving us nuts. We have an old VB2005 application which only needs a new RDLC report adding.
However to add the RDLC we need to add a new data source. Every time we try to add a new datasource using the Object option (not dataset) we get this error:
Now, you can get some help on Google for this but a lot of it is for web projects. This is a Winforms project.
Here's what we've tried:
devenv.exe /ResetSettings
checking the Assembly name doesn't have any punctuation or weird characters in it (this is a favourite solution from Google) - it doesn't
removing the source control (Perforce)
rebuilding the project from scratch
Our solution was to upgrade the project to VS2008. Didn't really want to as we feared destabilising the application in unpredictable ways just to achieve an edit in a report.
But in fact the upgrade did solve the data source problem, and so far at least, there haven't been any side effects.
I've been following the tutorial videos for DotNetNuke and i am at the part where i am now creating my own modules. I've installed everything i need to and put the template in the required folder, but whenever i try to create a project it comess up saying
"The local IIS URL http://dnndev/desktopmodules/... specified for Web project ... has not been configured"
It then asks me to create a virtual directory but says i cant because the server "http://dnndev" is not on the local machine.
I've searched for answers for a while now and have tried editing the template file and the host file but no matter what i try i always get the same message back. Does anyone know how i can fix this?
Thanks
If you follow these steps for setting up your Development environment than the templates should work as is.
http://www.dotnetnuke.com/Resources/Wiki/Page/development-environment.aspx
If you are using a different path for your website I would recommend customizing the templates.
http://www.dotnetnuke.com/Resources/Wiki/Page/Customize-Project-Template.aspx
I assume you are using dotnetnuke wiki page link which seems confusing. For better steps go to: http://www.dotnetnuke.com/Resources/Blogs/BlogID/16.aspx and locate "Let's Build a Module #1 - Project Introduction" which is a first video in step by step series of videos which will help you to clearly understand the process.
Let me know if you need more help.
I started a trial of Sencha Architect, and the more I use it more questions come to my mind for its actual feasibility usage in a development environment, one of the bigger questions I have is
In an environment that you can't edit the individual files in different editors, how can multiple people collaborate in developing different parts of a site, for example
app/models|components|views/Model1.js <- In charge of developer one
app/models|components|views/Model2.js <- In charge of developer two.
In a regular environment you could use git, for example, to distribute each file but in architect, you are not expected to edit files manually (which sucks because features like profiles are not exposed in architect). If you do edit them manually, it will cause problems or it may overwrite your code back to whatever data is on the project file so I am wondering what is the proper, or expected collaboration workflow with Sencha.
Having read the above posts, I still can't believe that keeping Sencha
metadata files in code repository and generating ALL JavaScript from metadata is suitable for big projects.
The idea of Sencha Architect is to keep the code not in javascript files, but in JSON metadata, and whenever you need to edit a JavaScript code, you have to use IDE and edit metadata. Phil Strong said "We ask that you continue to use Architect as your editor and doing so with 20 engineers is perfectly safe using Git or SVN.". Of course this workflow is very profitable for Sencha, it forces 20 people to use a licensed Sencha Architect, because to change a single line of JavaScript code the developer must use Sencha Architect.
When two people edit the same file, IDE updates metadata. Then they check-in the file into a code repository, and one of them has to resolve conflicts, so the developer has to merge two metadata files, not JavaScript files.
The whole idea of not letting developers to edit JavaScript unless they use Sencha Architect is counter-productive, because the same person can be using his favorite IDE for both Java and JavaScript development, or Python and JavaScript. Doing both client and server programming in the same IDE is faster than switch between two IDE's. The reality of a big project is that you have multiple teams around the globe who work with different IDE's, you also may have a short-term project implemented by a contractor who also has his favorite IDE.
ExtJS is a well designed framework, you don't need SenchaArchitect to modify a single line of JavaScript code.
When coding in JavaScript, I save my JavaScript file and refresh browser, and see the changes immediately. Sencha Archtect adds and additional step, it requires you to publish
javascript (generate JavaScript from metadata), and the bigger the project is, the longer is delay. Often I have to modify JavaScript files in production, sometimes changing a single line fixes the problem, again, I have to use Sencha Architect to re-generate this single line from metadata.
I use Sencha Architect for quick prototyping only, then check-in generated files into code repository and continue to edit JavaScript manually. With this approach I can use a version control system to see the history of JavaScript. If I checked in JSON metadata into
a VCS, then I would not have the history of JavaScript, I would have the history of JSON metadata which is counterintuitive.
I think that having metadata for GUI form is OK, but the limitation that MVC controller level has also to be generated from metadata is not OK.
While I appreciate very much Sencha's effort in creating useful and full-featured dev environment I don't think Sencha Architect is quite ready for relatively big projects and teams of developers.
I original Architect software very useful for quick prototyping and designing complex UI structures, but then again - after you figure out the way your UI elements will lay down in JS file - often it's easier and faster to copy-paste existing JS code.
I don't think this is the answer you were looking for, I just wanted to share my thoughts.
When I had searched for this same topic, I had found that it is the metadata/ directory that is the important meat of the project, and that all of the components are separated out into their own metadata files. This, along with the root level project files, is probably the important part for version control. The app/ is regenerated on save and probably can be excluded from version control.
The main xds project file containers more general references and will probably change less often than the metadata components. But it would change when new components are created or project/app level settings are modified.
Ideally, if you just check in the root files and the metadata folder, it should just work.
Working in a team with source/version control is quite easy with Sencha Architect. An Architect project is all enclosed in a project directory. Inside it's made up of n parts
project file - consists of a small amount of data used by Architect to open and maintain your project. It's the single file you can double click to open it
metadata directory - consists of the files that describe all the pieces of your project. Each class (controller, view, model, store, resource) has it's information stored in it's own file.
app directory - consists of the src of the project you've created. A javascript file for each class.
other root files - an app.html and app.js which is the launchpad for your application and what get's run when you preview your application. This is also where your packager.json, app.json would go.
The point of me describing all of this is to show you that the files generated by Architect are pretty much identical to what you would have created in your favorite editor by hand. The only additional information is the metadata and the project file. The metadata is all JSON.
FOR NOW!!
We ask that you continue to use Architect as your editor and doing so with 20 engineers is perfectly safe using Git or SVN. When a dev makes a change it changes both the metadata and the app for those files.
I asked the same question to Aaron from Sencha in a private message. He suggested to check in the entire project structure including app and metadata.
It works, we did one flow in our team.