weblogs.asp.net
Thursday, February 25, 2016 12:07 AM

VS2015-Templates

I’ve been maintaining my DotNetNuke Visual Studio project templates for a number of years now, one of the things they have sorely been lacking is the ability to “customize” the templates without having to crack open the full source code of the VSIX project, making changes, and then recompiling everything. There are 5 specific strings/values that were ripe for customization, but simply were not easily accessible.

  • Root NameSpace – The Namespace for the project, all of the files were populated with this namespace.
  • Owner Name – A DNN Manifest property that is used to provide information on who either developed the module, or commissioned the module development. This also gets used in all of the Copyright statements built into the templates.
  • Owner Email – Another DNN Manifest property, used to provide an Email address for contacting the owner/developer of a module.
  • Owner Website – The URL of the package’s owner, for further contact and information.
  • Local DEV URL – The URL of your local development environment.

Of all of those items, the one that has likely caused the most headache over the years is the Local DEV URL property, that was set at DNNDEV.ME, which if you followed along with my various tutorials, was the URL I always use for local development, that domain name points to 127.0.0.1. This actually works out great, but some people choose not to follow my tutorials or already have existing development environments configured, yet still want to use my templates. You could still use them, but you had to make some modifications to the PROJ files after creation in order to get things working.

With the latest release of the templates, when you create a project using one of the 6 included templates, you will then be prompted with a Wizard interface (single step) that will allow you to customize these fields.

TemplateCapture

As always, you can download the latest “release” of the templates from the DNN Store, or from the Visual Studio Online Gallery if you want to get creative, you can check out the Repo on GitHub

Project350z
Tuesday, February 16, 2016 1:03 AM
350z with XXR 531 18x11 wheelsEarlier today I took the leaking wheel/tire to Solo Performance Specialties to take the tire off the rim and take a look at the wheel and see what the damage really was. After popping the tire off the wheel we quickly found that the wheel had a repair attempted both inside and outside of the wheel, it actually looked like someone had taken JB Weld to it.
Chris Hammond
Wednesday, January 20, 2016 8:29 PM
With the release of DNN Platform 8 last week it is now possible to develop modules using SPA and MVC patterns within the DNN platform. As Part of the buildup of the DNN 8 release, Will Strohl provided a Pull request to my DNN Extension Project Templates project to help clean up some of the basic module templates to work better on Windows Azure environments, and to prep them for inclusion of new DNN 8 specific templates for SPA and MVC modules. Early in the fall Joe Brinkman provided a partial SPA project, with the intention of it becoming a project template. I had a little time when it was initially submitted to work on it, but wasn’t able to get everything squared away on the template until early December. It wasn’t until last week that I got additional time to do further testing on the template and fix a few issues that occurred during the conversion to a project template.
Project350z
Sunday, January 03, 2016 11:41 PM

image

When I picked up the 350z in Chattanooga back in November, I figured out that the radio wasn’t great, the sound was weak, and it didn’t appear to pick up any FM signals whatsoever. Over the Xmas weekend I decided it was time to rip into the car to remove the stock Bose amp and subwoofer (behind the driver’s seat) as well as try to tack down why the FM reception was non-existent.

The first step was to get into the subwoofer location behind the driver’s seat, a quick screw driver inserted into the panelling to pop the cover off. pry and then pull it off. Once I removed the cover, I quickly found that the stock Bose setup had already been removed, I figured that might be the case, but wasn’t 100% sure until we pulled the cover off. While in there I took the time to clean up some of the stray wiring that was in there, some exposed wires, and some live power wires that simply had electrical tape wrapped around them.

After working on the (lack there of) Sub, it was time to rip into the dashboard. I’ve done it so many times on my prior 350zs that it is straightforward and fairly painless to do. The one thing that gave me trouble was disconnecting the wiring harness from the center console where the harness powers the hazard, and seat warmer switches. I ended up pulling the panel up and off of the emergency brake in order to get to the plug for the wiring.

Once I pulled the plastic for the console out of place I dug in behind the stereo itself. First thing I checked was to see if the antenna wiring was plugged into the head unit, unfortunatly it was, so that wasn’t going to be an easy fix! I tracked down some wires from the stereo by pulling down the manual from the Pioneer website.One thing I did find was there is the “mic” for the handsfree bluetooth setup was plugged into the “wired remote” port on the back of the head unit. I unplugged that, but unfortunately couldn’t plug it into the proper MIC input as the jack was the wrong size. I plugged the mic back into the W/R port and started playing around with the headunit to see if I could get any stations tuned.

While digging in the center console compartment I found a wireless remote for the stereo, thinking that might work with “options” better than the touch screen I try to start using that, with no success. I checked the battery in the remote, and found it was a CR2016, but the remote said it took a CR2025, so I grabbed a spare and popped that in place. Ends up, that didn’t work either, no matter what I tried I couldn’t get the remote to work. Until I once again unplugged the mic from the “wired remote” port, one I did that the remote started working properly. So apparently whomever installed this radio, the wiring was done incorrectly on the MIC, and that was causing problems.

I went ahead and left the MIC unplugged and put everything back together in the car. I immediately tried to tune FM, and found that I could actually tune to a specific station, where previously I was only able to scan, and with the lack of signal previously, the scan would continue until manually stopped by switching input sources. I still wasn’t able to get a clear tune on a station, but when I pulled the car out of the garage to reposition where it was parked, I did find that it started to get a signal to a local radio station here.

So it looks like the ultimately problem with the radio may just have been the miswired Mic, we’ll see, next time I drive the car, how things play out. It might be a while though before I get back out in the Z, it has turned cold here in Missouri and I don’t plan to drive the car too much in below freezing temps, due to the abuse on the tires.

HorsesAndCars.com
Saturday, January 02, 2016 11:01 PM

So here we sit, 2 years since our last Christmas card, or has it been longer? Probably just two. This is the start of year #2 in our home in Wildwood. We moved into the house in November 2014 and have been loving it out here on the far side of West County ever since.

RSS URL

Chris Hammond is

Chris Hammond is a father, husband, leader, developer and car guy. Chris has long specialized in ASP.NET and DotNetNuke development, so you will find a variety of topics here on the website. For more information check out the about me page.

If you are looking for DotNetNuke consulting please visit my business website at http://www.christoc.com/

Latest Photos

Follow Me Facebook Me Plus Me

Disclaimer

Any blog posts here are solely the opinion and views of Chris Hammond only. Comments on blog posts are the opinion of the commenter, and not Chris Hammond.

DotNetNuke Hosting

Hosting for this website is provided by AppliedI.Net. Be sure to visit them for all your DotNetNuke Hosting needs. 

Powered By

This website is managed by Christoc.com Software Solutions

Find Me