Not sure why but for some reason Umbraco is creating multiple copies of templates, all of which are blank.
Sorry a little vague but haven't got much to go on. Any ideas?
Related
I am trying to extend the Multi Node Tree Picker (MNTP) in Umbraco but am running into some trouble. I am used to writing property editors in the new umbraco 7 angular style, so the MNTP is a bit foreign to me. I want to be able to connect my uCommerce Catalog Tree to the MNTP. I feel like this should be fairly simple as all that I should need to do is hook up the uCommerce tree to the MNTP. I am in the Umbraco.Web.PropertyEditors dll, but it isn't really helping me too much. Any pointers to get me started in the right direction would be much appreciated. I could then share this as a new package if I can get it working.
Thanks!
I would recommend creating your own property editor that simply uses the Umbraco dialogService to pick the uCommerce product.
You can use the Yo Umbraco template generator to build a scaffolded package:
https://github.com/warrenbuckley/generator-umbraco
This might be a weird question to ask.. but nevertheless this is my question.
I have a huge Asp.net MVC project with lots of model classes. As the requirement grew, we kept on adding some properties and deleting some. Eventually I ended up having properties which are not referenced anywhere in the project.
Is there any quick way to find out these orphan properties.?
ReSharper can do this. Right-click on your solution and selection "Find Code Issues".
One of the results is "Unused Symbols". This will show you classes, methods, properties etc., that aren't used.
I would use resharper to assist you with this task. In case you don't want to spend the $349 you can use it for 30days for free. Resharper allows you to analyse the whole solution and highlights obsolete/unused code.
I've created a web app (mvc4) that I'd like to reuse in multiple projects. The site is an admin panel, but it may be extended and slightly modified in each project. I want to avoid copying the project over, because I'd like to be able to update each project to the latest version at the lowest possible cost.
So far I have tried 2 approaches:
a script that 'clones' the project by copying all the necessary things as well as altering others (guids in assemblies, namespaces and things like that) - this works fine for extensibility and modification, but that's just a copy so pushing 'updates' is a mess (I did it manually) and it does not scale.
portable areas from mvc contrib project - this seemed like a good idea at first, but it turns out that it's nice for simple scenarios, but fails at more advanced use cases. It doesn't support localization (from resources embedded in the portable area), bundling and min requires a lot of hacks (mvc contrib is still on mvc 3), it's not possible (out of the box) to reuse shared views or Display/Editor templates from the portable area and it looks like if I'd go further that way, some new things would come up
Currently I'm thinking about 'just' branching each project from the core one. This would of course require the same changes (or at least a big subset of them) that were done in the script I mentioned earlier, and I'm afraid that if I try to pull updates from the core project the number of conflicts will render the whole approach unusable.
Does anyone have an idea on how I could tackle this problem?
I'd suggest to create a NuGet package of the mvc app and reuse it. So versioning and applying updates would be much easier. However it takes a bit work to make your code completely isolated from the codes you want to add in the new project.
I am finalizing a MVC project and have switched to using Google's CDN for jQuery. After doing that, do you delete out the unused .JS files from the scripts folder?
Did you leave all the extra default plumbing visual studios adds for the controllers, views, models that no one ever uses? (i sure hope you answered no)
that should answer this question to. no sense having stuff your not using laying around.
I personally keep them around, so that if I go back to development and want to reference the scripts locally again, I can do that without getting them in place all over again.
I'd leave them around whilst developing (just in case...) but once finished and sure I won't need them I'd delete them. It's only going to cause confusion for other developers if they assume you are referencing them locally as they've seen them in the Scripts folder. If you are really squeamish about deleting them, I guess you could always exclude them from the project - but really I see no point so delete 'em!
Maybe this applied to other Delphi's (I've only used 7). We've got our code broken up so that nearly every DLL in our fairly massive app is in a different folder.
99% of the open source stuff I've downloaded to plug into Delphi have had all their source munged into one folder.
It seems like this was an assumption that the developers of Delphi made about the coding practices of it's users that may be non-obvious.
I don't think so. In fact, In more recent versions they've added features to the project manager to make it easier to deal with the fact that code is spread around different directories (such as the flatten directories option), so I think it is accepted that this is how many people organize their code.
I suspect it's more to do with projects growing organically over time, and whether anyone takes the time to tidy up.
I for one definitely do not put all the sources into one directory but rather keep them in groups that have something in common. e.g. I use subversion externals quite extensively
(see http://www.dummzeuch.de/delphi/subversion/english.html , the section about externals).
I prefer different modules to be hosted on different folders, then have a common folder for units that is shared among different modules, makes management easy. e.g
myClientServerApp:(parent)
Client folder :(child)
server filder (child)
lib - (child)
Back in DELPHI 7 I also had all files in one folder. It has easy for small projects, but very hard for med to big one.
So I began to create a folder structure for all DELPHI projects small or big.
Over the year I am trying to improve, this folder structure, and every new project I make a small improvement so that it is simpler, logical, and more organized.
This day I am trying to make some parts of it sharable to several project. Its work in progress.
It would seem that having all the units in one folder would save you headaches in doubly named units. On the other hand, it might be handier to keep your projects in different folders when checking in and out of your version control. On the other hand it really doesn't promote code reuse to have them separated out like that.