Sometimes the first request to the application results in exceptions like 'No connection could be made because the target machine actively refused it'. Adding a retry to mitigate that.
- Upgraded to Angular 1.3 (Fixes#267)
- Fix XHR GET caching issue in IE with new NoCacheAttribute
- Slight fix in admin home page (album list) to ensure initial data fetch has the sort expression in the query
When file names are missing from exception stack trace the above line of code does not pass the detected function name. As a result issue described in bug : https://github.com/aspnet/Diagnostics/issues/49 happens.
This issue happens on mono. With this fix method names show up in the error page middleware output on mono.
This is a sample of the pattern for building a MapRoute method that
customizes routing by adding constraints, datatokens, or defaults. This is
the replacement for adding data to the route directly.
Also fixed up the sample to work. It was massively out of date.
The properties on TemplateRoute for DataTokens and Defaults are now
readonly. This prevents modifying these collections in a way that
invalidates cached data, or violates thread-safety.
To do the same for constraints, this change includes a substantial refactor
of how we realize inline constraints, and moves the constraint resolver
out of the parsing phase.
This allow creates a builder for the constraint map, that will make it
easier to implement features like optional constraints, and is reusable
for anyone building their own type of routing system.
These tests verify that per-request services can be injected into assets
that users provide/implements (filters, constraints, controllers, views,
etc).
The purpose is to verify that the services are correctly resolved from the
per-request service container, and don't have state that lingers and
influences the next request. This is important because changing the
lifetime of a framework services could easily impact the lifetimes of
others, and ultimately of something the user created.
Rather than throwing here, this does what routing does. If request
services aren't set, we just create our own scope.
This will NOT create an extra scope if request services are already set.
- Modified our default TagHelperDescriptorResolver to provide a protected virtual method that it uses under the covers to resolve descriptors for an entire assembly. This will enable tooling to cache descriptors on a per-assembly basis.
#214
- Right now the only information that is used from the PropertyInfo is the PropertyName and the PropertyType, therefore changed the PropertyInfo property on TagHelperAttributeDescriptor to be AttributeTypeName since we already had an accessor for AttributePropertyName.
- Modified test comparers to validate type names.
#214
- TagHelperDescriptor's need a way to showcase where they came from so tooling can reverse look them up.
- Update tests to specify TagHelperDescriptor assembly names.
#214
Ajay Bhargav Baaskaran
Praburaj
N. Taylor Mullen
DamianEdwards
ianhong
Suhas Joshi
Pranav K
rowanmiller
Chris Ross
Ryan Nowak