October 11, 2016 at 1:16 PM
Sometimes you will come across a situation where you debug in Visual Studio and you are unable to look at the variables. You simply get a message that reads:
"Could not evaluate Expression"
Long story short, one of the reasons this happens is corrupt breakpoints.
Pull up your Breakpoint window and erase every single breakpoint you have. Compile and set your breakpoints again.
Problem solved. :-)
September 6, 2016 at 1:04 AM
If you are reading this, chances are you have figured out by now that GoDaddy does not allow external mail relay.
In other words, if you try to use an external mail server to send e-mail, it won't work.
Fortunately, the solution is simple:
Use their mail relay.
If you are like me, however, you are probably confused as the GoDaddy relay server uses network delivery which means it does not use a username and password.
To get this to work, use the following settings:
- E-mail Address: email@example.com
- SMTP server: relay-hosting.secureserver.net
- Port Number: 25
- Username: [BLANK]
- Password: [BLANK]
([Blank] = Do not enter anything, leave empty)
June 23, 2016 at 9:51 AM
Recently, I was comparing two CSV files. I wasn't interested in orphan rows (rows that existed in one file but not the other). I only wanted to see what had changed in records that existed in both.
I found a few articles but they were all outdated. I eventually figured it out so I thought I would share it with you:
- Right click on the toolbar on top (bar with icons like Next Diff)
- Select Toggles
You should now see additional buttons on the toolbar that allow you to show/hide orphan rows on either side, among a few other things.
So apparently the bar that loads by default is the "Favorites" one. Counter-intuitive if you ask me.
Awesome product, nevertheless.
October 8, 2015 at 9:54 AM
I have rules configured in Outlook that move e-mails to different folders. One of these folders was reporting an unread message but the folder content view showed all messages marked as read.
It turns out there is a very simple way to fix this. There is in fact an e-mail that is not marked as read. You can find it by accessing the web version of the product, which is commonly available in company deployments. The URL is usually:
Once you find it, mark it as read on the web interface and Outlook will automatically refresh and no longer show unread messages.
August 9, 2015 at 3:42 PM
I came across a situation where I could not login to AspDotNetStoreFront. It kept redirecting me back to the login page with no apparent error message, which seemed to indicate that the login was successful, yet it wasn't doing anything.
The issue turned out to be the time zone difference between web server and database server. I was running my copy locally and the time at the server was running a few hours behind, which causes the application to think you have "timed out".
To work around this, there is an application setting named "SessionTimeoutInMinutes" that you can change to a value greater than the time zone difference, in order to keep the session active.
I had trouble locating this setting. Eventually I figured out it used to live in a configuration file apparently, but it now has been moved to table "AppConfig" in the database. Change the "ConfigValue" column value and it should allow you to log in.
Make sure to restart the application afterwards to force reloading of the settings.
August 6, 2015 at 10:18 AM
You may run into a situation where you have configured your site to run Windows authentication but you get an authentication error when you try to browse it during a debug session.
To fix this issue, you need to edit the Application Host file for IIS and enable Windows authentication. You can find the file here:
Find the <security> section inside the <system.webServer> node and enable Windows authentication as follows:
<windowsAuthentication enabled="true" />
And that's all there is to it. :-)
May 18, 2015 at 11:41 AM
It turns out there is a very simple way to inspect the Angular scope for a particular HTML element if you are using Chrome.
Simply right click on an element on the page, select inspect element, switch to the console tab and type the following:
Alternatively, you can select an element from the HTML tab and then go to the console and type the script command.
May 12, 2015 at 10:56 AM
I was working on a project that involved ASPDotNetStoreFront's MultiStore product and for one reason or another, my account was locked and I could not get into the administration interface.
Sadly, my account was the only Super Admin account.
Fortunately, there is a procedure that can be followed on the backend in order to reset the super admin account:
- Open the database with a tool that allows you to run SQL scripts, such as SQL Management Studio.
- Run the following query:
Restart the site by recycling the application or modifying the web.config file.
SET [Password] = 'YOUR NEW PASSWORD',
[SaltKey] = -1,
[LockedUntil] = DateAdd(mi, -1, GetDate()),
[BadLoginCount] = 0,
[PwdChangeRequired] = 0,
[PwdChanged] = GetDate()
WHERE [Email] = 'SUPER ADMIN EMAIL ADDRESS'
And that's all there is to it. Go back to your admin console and login normally.
March 12, 2015 at 10:54 AM
I am using Umbraco as the CMS for a project and came across a curious situation:
I noticed my changes to templates seemed not to be saved for some reason.
- I opened the template
- I modified its contents
- I hit save
- I got the message that the changes were saved successfully
- I could see the new version displayed on the published site
- I get back into the template to edit it, I get the old version instead of what I saved.
Well, It turns out it's a caching issue. The contents are in fact saved which is why you see them on the site.
Don't ask me what Umbraco does with caching because I don't know and quite frankly I don't have the time to find out. Suffice it to say, cache is the issue.
To fix this:
- Log out of the Umbraco site
- Clear the cache
- Log back in
Chrome has a checkbox inside the settings of the development toolbar that allows you to "disable the cache" which is the same as deleting it for the current site.
October 9, 2014 at 1:28 PM
As it turns out, using the ubiquitous string.replace() function does not work as it only replaces the first occurrence.
As it turns out the following pattern can be used to achieve this:
So, let's say I have the following variable:
var template = "This is just some hard text because it's hard to read but not so hard to write";
And I want to replace all occurrences of "hard" with "soft". I would do:
template = template.split("hard").join("soft");
The result is:
"This is just some soft text because it's soft to read but not so soft to write"
Pretty clever piece of code. It works like a charm. I wish I had thought of it myself...
The original article where I found this solution can be seen here.