Many of you won’t care too much about creating Portal Specific Modules because you’ll be creating modules for an environment that only has one portal. However, if you are creating a module for resell, or you will be using the module in a multi-portal environment, you’ll need this next piece of information I’m going to give you.
If you're new here, you may want to subscribe to my RSS feed. Thanks for visiting!
If you’ve been avoiding using JSON in your ASP.NET application because you think it’s hard, you’re an idiot. I can say that, because I’ve been avoiding it for exactly that reason. I’ve been an idiot too. But no more! Using an UpdatePanel is still easier than JSON. But JSON is easy enough that you may decide to use it over the UpdatePanel under certain circumstances.
Now that we have our tables created, we are going to use the CodeSmith product that we installed last week to create our stored procedures.
We will also end up creating the SQL scripts that we will need to install this module into another DNN installation.
One of the big mistakes I see young programmers make is writing code that they should never have written. While the code was a great educational exercise, it was a waste of the employer’s money. So how do you decide what code to write and what code to leave out?
Here are some simple rules to follow that will make you an asset to your company. If you want to be the last one they fire, make sure you are the most efficient programmer.
On Tuesday we installed the free version of CodeSmith to help us create the database access code. Before we can create the access code, we need some tables in our system. Even if you think you know all about creating tables in a database, don’t skip this lesson. There are some very specific tips related to working with DotNetNuke that you will miss if you skip it.
