Upgrading from to 1.6.313

Topics: Installing BugNET
Jun 19, 2014 at 6:30 PM
I am currently trying to upgrade my company's own version of BugNet from 1.1 to 1.6 and am having a few problems making that happen. My steps so far are the following:
  • Backup site, db
  • Copy the contents of the BugNet Upgrade/BugNet folder from the installer zip to the directory with the current site on it.
  • Copy the old connection string over to the new web.config.
  • Load up the site and click on login (it links to login, not login.aspx, and 404s)
  • Visit login.aspx, log in, get an error about needing a providerName in my connection string, set it to "System.Data.SqlClient"
  • When I try to log in again (still visiting login.aspx specifically, login alone fails) the page does nothing.
This is what inspect element shows me when errors from HTML and js are on. CSS are hidden.
GET http://localhost/bundles/modernizr [HTTP/1.1 404 Not Found 23ms]
GET http://localhost/Content/css [HTTP/1.1 404 Not Found 25ms]
GET http://localhost/Content/css [HTTP/1.1 404 Not Found 28ms]
GET http://localhost/bundles/WebFormsJs [HTTP/1.1 404 Not Found 44ms]

If any more information is needed to get a good answer, I'll get it.
Jun 19, 2014 at 6:37 PM
Copying over the contents probably isn't the best way to upgrade anymore due to new / deleted files. Sounds like some of the files didn't get overwritten etc.

Backup your installation,
delete all files ,except the uploads folder.
Merge the web.configs , your connection string.
Jun 19, 2014 at 6:47 PM
Edited Jun 19, 2014 at 6:50 PM
I've done all that you said, keeping only the uploads folder from the old install and merging the web.configs while retaining the old connection string and it still does not append .aspx to urls, causing the 404s, and also cannot get past the login page. I also had to add "System.Data.SqlClient" to the providerName in the connection string again.
Jun 19, 2014 at 6:50 PM
Jun 19, 2014 at 6:55 PM
Well, this is running on the same setup 1.1 was working just fine on. I'd like to know why friendly urls are not working either. http://localhost/Account/Login is what it goes to, by the way.