Thanks for the update.
↧
New Post: Use of Release Notes
↧
New Post: Configure Source Code Repository Integration
I see, but please help me clarify this. When configured correctly, (I'm getting error Application Error - /BugNET1.6.315/SvnBrowse/SubversionBrowser.aspx), every comment to an issue and every change in an issue, it will appear in the Repository?
Or is it the "Source Code" of the tool (meaning the programming code).?
Or is it the "Source Code" of the tool (meaning the programming code).?
↧
↧
New Post: Problem upgrading from 315 to 329: Directory does not exist. Parameter name: directoryVirtualPath
I have upgraded this without trouble at least ten times before.
This time I backed up the database and followed the usual instructions. My install is a stock SQL Server install - nothing fancy, upgrades have been 100% reliable etc.
However on restarting the new 329 website, I get the following error/ YSOD. Fortunately it looks like this is the initial compile of 329, so it did not as far as I can tell change the database, in so much as I did not restore the backup, but 315 still seems to work with the database as is. Any ideas? Looks like there's some new bundling code in there which doesn't work if the site is stand-alone (not in a virtual folder).
Here's the error:
This time I backed up the database and followed the usual instructions. My install is a stock SQL Server install - nothing fancy, upgrades have been 100% reliable etc.
However on restarting the new 329 website, I get the following error/ YSOD. Fortunately it looks like this is the initial compile of 329, so it did not as far as I can tell change the database, in so much as I did not restore the backup, but 315 still seems to work with the database as is. Any ideas? Looks like there's some new bundling code in there which doesn't work if the site is stand-alone (not in a virtual folder).
Here's the error:
Server Error in '/' Application.
Directory does not exist.
Parameter name: directoryVirtualPath
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.ArgumentException: Directory does not exist.
Parameter name: directoryVirtualPath
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[ArgumentException: Directory does not exist.
Parameter name: directoryVirtualPath]
System.Web.Optimization.Bundle.Include(String virtualPath, IItemTransform[] transforms) +136
BugNET.BundleConfig.RegisterBundles(BundleCollection bundles) +587
[HttpException (0x80004005): Directory does not exist.
Parameter name: directoryVirtualPath]
System.Web.HttpApplicationFactory.EnsureAppStartCalledForIntegratedMode(HttpContext context, HttpApplication app) +12951237
System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers) +175
System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context) +304
System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context) +404
System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext) +475
[HttpException (0x80004005): Directory does not exist.
Parameter name: directoryVirtualPath]
System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +12968244
System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +159
System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) +12807949
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.18446↧
New Post: Problem upgrading from 315 to 329: Directory does not exist. Parameter name: directoryVirtualPath
There's another post here which suggests it's (now) mandatory to put this in a virtual directory. It was previously not so. If that's true, then that could be what is causing this - it looks like the bundling code you have there is assuming there is a virtual directory. When our users go home I can try to install the stuff somewhere else then put it in a virtual directory on IIS, maybe that will fix it.
↧
New Post: Problem upgrading from 315 to 329: Directory does not exist. Parameter name: directoryVirtualPath
philw wrote:
There's another post here which suggests it's (now) mandatory to put this in a virtual directory. It was previously not so. If that's true, then that could be what is causing this - it looks like the bundling code you have there is assuming there is a virtual directory. When our users go home I can try to install the stuff somewhere else then put it in a virtual directory on IIS, maybe that will fix it.BugNET has always required that you create a virtual directory and configure it as an application in order to execute asp.net properly. This hasn't changed between the releases so I am unsure why you receive that error.
↧
↧
New Post: Problem upgrading from 315 to 329: Directory does not exist. Parameter name: directoryVirtualPath
<shrug> It has worked previously without issue, as a simple website. This new version appears to change that; the previous version still works fine as a simple website.
↧
New Post: Adding users to notifications
asudman wrote:
The documentation says "This list can be modified by those who have proper permissions."...but what are those "proper permissions"?? Is it the 'super user' flag? Can the notification list only be updated by an admin user and/or the creator?Super user's or the project administrator's can use this function.
Thanks!
↧
Updated Wiki: Adding and Editing Issues
Adding and Editing Issues
To add a new issue click the new issue from the menu. If you don't see this menu item either you are not logged into BugNET or you do not have the proper permissions to create new issues. Permissions are given via the project roles and permissions pages that an administrator will have to grant you.The new issue screen will display all drop down lists as configured by the default properties page in the project administrator page and a full rich text editor to enter the description of the issue. The new issue screen also allows you to select a file attachment to upload to the issue during creation.
The only required field on the default issue screen is the title (unless there are mandatory custom fields configured for the project)
Clicking save after selecting all the desired values will save the issue, send a new issue notification to all users that are subscribed to the project notifications, and then take you to the issue detail page. If you click save and return you are redirect to the issue list after saving the issue.
Editing Issues
To edit an issue, select an from the issue list or search and you will be taken to the issue detail page. On this page you can edit the details of an issue and save, or delete the issue.The issue detail page offers more information about a history and its lifetime. Several tabs are at the bottom of the screen that contain more information about the issue.
Comments
The comments tab contains all the comments that users have entered on this issue and allows you to enter a new comment.Attachments
The attachments tab shows a list of attachments that have been added to this issue and allows you to upload new attachments.History
The history tab shows a list of changes to this issue, by whom and on what date.Notifications
The notifications tab shows a list of users who are subscribed to receive updates when this issue is modified. A user can subscribe or unsubscribe themselves from notifications on the issue.The notifications list can be modified by those who have proper permissions (Super user's or the project administrator's)
Sub Issues
The sub issues tab shows a list of issues that are children of this issue and allows you to add a new sub issue.Parent Issues
The parent issues tab shows a list of issues that are parents of this issue and allows you to add a new parent by the issue id.Related Issues
The related issues tab shows a list of related issues and allows you to add a new related issue.Revisions
When source control integration is configured, any commits to the source code repository identified with the issue id are added to the list of revisions.Time Tracking
The time tracking tab shows a list of time logged entries for an issue and allows you to added new time entries. The sum of the time logged entries is reported on the issue detail time logged field.↧
Source code checked in, #d8a7c87c70ab
moved identity config to busines logic libary.
updated authentication module to be async
added new tables to database project
↧
↧
New Post: Problem upgrading from 315 to 329: Directory does not exist. Parameter name: directoryVirtualPath
Ok, so I un-installed it all and repeated the documented steps in the install guide here, and I still get the same error. I don't really want a virtual directory, or the alias which comes with it, but even if I have one, I'm getting the same error. I guess this upgrade isn't going to work for us. Either someone else will have the same problem, or if it's just us then we can try to fix it in a future release, or look at other options, but this one doesn't work for us I'm afraid. It looks like the bundling code.
↧
Created Unassigned: How to import tasks from an excel workbook or csv into BugNet. [265]
How to import tasks from an excel workbook or csv into BugNet. Kindly help me.
↧
Commented Unassigned: How to import tasks from an excel workbook or csv into BugNet. [265]
How to import tasks from an excel workbook or csv into BugNet. Kindly help me.
Comments: BugNET doesn't have this feature. You would have to look into importing it some other way.
Comments: BugNET doesn't have this feature. You would have to look into importing it some other way.
↧
New Post: No App_Data folder in installation...
The installation instructions for sql lite refer to a Bugnet/App_Data folder containing the sql lite database... There is no such folder in the zip file.
Should I retrieve it from source control and add it?
Should I retrieve it from source control and add it?
↧
↧
New Post: No App_Data folder in installation...
patniemeyer wrote:
The installation instructions for sql lite refer to a Bugnet/App_Data folder containing the sql lite database... There is no such folder in the zip file.I believe you mean sql server express, and you can ignore the app_data folder. By default, sql server express stores its database under the sql server folder which is perfectly fine. The instructions were referring to using an attached database that used to be included in the App_Data folder from older install packages
Should I retrieve it from source control and add it?
↧
New Post: Columns in the exported Excel are fixed
clarence_17 wrote:
Thanks.
Is there a way to add/remove columns in the excel before exporting the list of issues? I tried to remove some columns in the tool, but after exporting to excel, the tool always have fixed columns.Export to excel does not show columns that have been hidden via the select / hide columns. Please list the steps to reproduce the issue you are having, the and the browser / version used.
I hope the next release will fix this.
Thanks.
↧
Source code checked in, #67f7233241bb
moved identity config to busines logic libary.
updated authentication module to be async
added new tables to database project
updated all nuget packages to latest versions
removed redundant profile admin user control
added isapproved and createdate fields to user table
deleted membership provider from the solution
↧
New Post: Could not load file or assembly 'DotNetOpenAuth.Core, Version=4.1.0.0
After upgrading (or trying to upgrade) to BugNet 1.6 I get the following error. I have searched the forums here and internet to no avail. I have made sure that .NET version 4.5 and 4.5.1 are installed, BugNet is using IIS App pool with .NET 4.0 selected. Cannot find what is causing this error.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.IO.FileLoadException: Could not load file or assembly 'DotNetOpenAuth.Core, Version=4.1.0.0, Culture=neutral, PublicKeyToken=2780ccd10d57b246' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Assembly Load Trace: The following information can be helpful to determine why the assembly 'DotNetOpenAuth.Core, Version=4.1.0.0, Culture=neutral, PublicKeyToken=2780ccd10d57b246' could not be loaded.
=== Pre-bind state information ===
LOG: DisplayName = DotNetOpenAuth.Core, Version=4.1.0.0, Culture=neutral, PublicKeyToken=2780ccd10d57b246
(Fully-specified)
LOG: Appbase = file:///C:/inetpub/wwwroot/bugnet/
LOG: Initial PrivatePath = C:\inetpub\wwwroot\bugnet\bin
LOG: Using application configuration file: C:\inetpub\wwwroot\bugnet\web.config
LOG: Using host configuration file: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet.config
LOG: Using machine configuration file from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\config\machine.config.
LOG: Post-policy reference: DotNetOpenAuth.Core, Version=4.1.0.0, Culture=neutral, PublicKeyToken=2780ccd10d57b246
LOG: Attempting download of new URL file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/Temporary ASP.NET Files/bugnet/e70c84d3/5b9ce869/DotNetOpenAuth.Core.DLL.
LOG: Attempting download of new URL file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/Temporary ASP.NET Files/bugnet/e70c84d3/5b9ce869/DotNetOpenAuth.Core/DotNetOpenAuth.Core.DLL.
LOG: Attempting download of new URL file:///C:/inetpub/wwwroot/bugnet/bin/DotNetOpenAuth.Core.DLL.
WRN: Comparing the assembly name resulted in the mismatch: Minor Version
ERR: Failed to complete setup of assembly (hr = 0x80131040). Probing terminated.
Stack Trace:
[FileLoadException: Could not load file or assembly 'DotNetOpenAuth.Core, Version=4.1.0.0, Culture=neutral, PublicKeyToken=2780ccd10d57b246' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)]
Microsoft.AspNet.Membership.OpenAuth.PreApplicationStartCode.Start() +0
[InvalidOperationException: The pre-application start initialization method Start on type Microsoft.AspNet.Membership.OpenAuth.PreApplicationStartCode threw an exception with the following error message: Could not load file or assembly 'DotNetOpenAuth.Core, Version=4.1.0.0, Culture=neutral, PublicKeyToken=2780ccd10d57b246' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040).]
System.Web.Compilation.BuildManager.InvokePreStartInitMethodsCore(ICollection
System.Web.Compilation.BuildManager.InvokePreStartInitMethods(ICollection`1 methods) +12967416
System.Web.Compilation.BuildManager.CallPreStartInitMethods(String preStartInitListPath, Boolean& isRefAssemblyLoaded) +280
System.Web.Compilation.BuildManager.ExecutePreAppStart() +172
System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters, PolicyLevel policyLevel, Exception appDomainCreationException) +1151
[HttpException (0x80004005): The pre-application start initialization method Start on type Microsoft.AspNet.Membership.OpenAuth.PreApplicationStartCode threw an exception with the following error message: Could not load file or assembly 'DotNetOpenAuth.Core, Version=4.1.0.0, Culture=neutral, PublicKeyToken=2780ccd10d57b246' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040).]
System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +12966756
System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +159
Assistance would be appreciated
Could not load file or assembly 'DotNetOpenAuth.Core, Version=4.1.0.0, Culture=neutral, PublicKeyToken=2780ccd10d57b246' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.IO.FileLoadException: Could not load file or assembly 'DotNetOpenAuth.Core, Version=4.1.0.0, Culture=neutral, PublicKeyToken=2780ccd10d57b246' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Assembly Load Trace: The following information can be helpful to determine why the assembly 'DotNetOpenAuth.Core, Version=4.1.0.0, Culture=neutral, PublicKeyToken=2780ccd10d57b246' could not be loaded.
=== Pre-bind state information ===
LOG: DisplayName = DotNetOpenAuth.Core, Version=4.1.0.0, Culture=neutral, PublicKeyToken=2780ccd10d57b246
(Fully-specified)
LOG: Appbase = file:///C:/inetpub/wwwroot/bugnet/
LOG: Initial PrivatePath = C:\inetpub\wwwroot\bugnet\bin
Calling assembly : Microsoft.AspNet.Membership.OpenAuth, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35.
LOG: This bind starts in default load context.LOG: Using application configuration file: C:\inetpub\wwwroot\bugnet\web.config
LOG: Using host configuration file: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet.config
LOG: Using machine configuration file from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\config\machine.config.
LOG: Post-policy reference: DotNetOpenAuth.Core, Version=4.1.0.0, Culture=neutral, PublicKeyToken=2780ccd10d57b246
LOG: Attempting download of new URL file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/Temporary ASP.NET Files/bugnet/e70c84d3/5b9ce869/DotNetOpenAuth.Core.DLL.
LOG: Attempting download of new URL file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/Temporary ASP.NET Files/bugnet/e70c84d3/5b9ce869/DotNetOpenAuth.Core/DotNetOpenAuth.Core.DLL.
LOG: Attempting download of new URL file:///C:/inetpub/wwwroot/bugnet/bin/DotNetOpenAuth.Core.DLL.
WRN: Comparing the assembly name resulted in the mismatch: Minor Version
ERR: Failed to complete setup of assembly (hr = 0x80131040). Probing terminated.
Stack Trace:
[FileLoadException: Could not load file or assembly 'DotNetOpenAuth.Core, Version=4.1.0.0, Culture=neutral, PublicKeyToken=2780ccd10d57b246' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)]
Microsoft.AspNet.Membership.OpenAuth.PreApplicationStartCode.Start() +0
[InvalidOperationException: The pre-application start initialization method Start on type Microsoft.AspNet.Membership.OpenAuth.PreApplicationStartCode threw an exception with the following error message: Could not load file or assembly 'DotNetOpenAuth.Core, Version=4.1.0.0, Culture=neutral, PublicKeyToken=2780ccd10d57b246' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040).]
System.Web.Compilation.BuildManager.InvokePreStartInitMethodsCore(ICollection
1 methods, Func1 setHostingEnvironmentCultures) +12967707System.Web.Compilation.BuildManager.InvokePreStartInitMethods(ICollection`1 methods) +12967416
System.Web.Compilation.BuildManager.CallPreStartInitMethods(String preStartInitListPath, Boolean& isRefAssemblyLoaded) +280
System.Web.Compilation.BuildManager.ExecutePreAppStart() +172
System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters, PolicyLevel policyLevel, Exception appDomainCreationException) +1151
[HttpException (0x80004005): The pre-application start initialization method Start on type Microsoft.AspNet.Membership.OpenAuth.PreApplicationStartCode threw an exception with the following error message: Could not load file or assembly 'DotNetOpenAuth.Core, Version=4.1.0.0, Culture=neutral, PublicKeyToken=2780ccd10d57b246' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040).]
System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +12966756
System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +159
System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) +12806561
↧
↧
New Post: Duplicate, ignore
Sorry, duplicate.
↧
New Post: Could not load file or assembly 'DotNetOpenAuth.Core, Version=4.1.0.0
Ensure that your web.config matches the one in the release package https://bugnet.codeplex.com/SourceControl/latest#src/BugNET_WAP/Web.config, especially the binding redirects section:
<dependentAssembly>
<assemblyIdentity name="DotNetOpenAuth.Core" publicKeyToken="2780ccd10d57b246" culture="neutral" />
<bindingRedirect oldVersion="0.0.0.0-4.3.0.0" newVersion="4.3.0.0" />
</dependentAssembly>↧
New Post: Columns in the exported Excel are fixed
I am using the latest version (1.6.329) and google chrome as my browser.
Sorry, it seems that I failed to click the Save Button before exporting. My apologies. Thank you.
Sorry, it seems that I failed to click the Save Button before exporting. My apologies. Thank you.
↧