Comments (23)
Date to start on this Issue: 07/07/2011
from nservicebus.
Nice touch with the label!
from nservicebus.
I have uploaded one package with symbol support; bu unable to validate for its correctness.
if my understanding is correct then we can upload one package with only symbol and source (full relevant source code) then the usual packages including PDB.
I experimenting more on this. Please put your suggestion if any.
from nservicebus.
To verify that it work create a new project install nservicebus with nuget and make sure that you can step into the nsb code. (you need to add symbolsource.org as a symbolsource in visual studio)
from nservicebus.
Do this one when the CI-packages is pushed to nuget. Pdb's should not be included
from nservicebus.
It seems that the src file is not getting sync may be the directory structure we upload the src file seems to wrong, is there any tool or way available to check the same symbolsource.org
from nservicebus.
I have no idea unfortunately. See if they have a discussion group?
On Wed, Nov 2, 2011 at 5:32 PM, Joseph Thomas <
[email protected]>wrote:
It seems that the src file is not getting sync may be the directory
structure we upload the src file seems to wrong, is there any tool or way
available to check the same symbolsource.orgReply to this email directly or view it on GitHub:
#53 (comment)
from nservicebus.
@Jpattom any news on this issue?
from nservicebus.
@john Simons I need start working on this again....
On 17/05/2012, John Simons
[email protected]
wrote:
@Jpattom any news on this issue?
Reply to this email directly or view it on GitHub:
#53 (comment)
from nservicebus.
I finally did more research on this.
Unfortunately we won't be able to publish symbols with our current build script + ilmerge of assemblies.
We would have to merge our sln/proj files into the correct number of binaries we produce to support publishing of symbols.
from nservicebus.
Given the bew project structure is this now possible?
from nservicebus.
@andreasohlund yes this is now possible
from nservicebus.
Please make this a priority, it's painful without.
from nservicebus.
@ianbattersby this is currently scheduled to be looked at again for v5.
Unless someone send us a PR before that 😉
from nservicebus.
I suspect my real issue is #1759, but having symbols hosted really should be a priority for you too IMHO - and 5.0 doesn't sound like it :-(
from nservicebus.
+1
from nservicebus.
@andreasohlund @SimonCropp should we have another bash at trying to get this to work?
I think the last issue we ran into was because of the pdbs not being ilmerged properly, but now that is fixed.
from nservicebus.
We need the source for all libs we ilmerge :(
Sent from my iPhone
On 17 dec 2013, at 22:38, John Simons [email protected] wrote:
@andreasohlund @SimonCropp should we have another bash at trying to get this to work?
I think the last issue we ran into was because of the pdbs not being ilmerged properly, but now that is fixed.—
Reply to this email directly or view it on GitHub.
from nservicebus.
@andreasohlund what happens if we only have symbols for our codebase?
from nservicebus.
It doesn't work because it complaints about not having the source for the
assemblies we ilmerging.
However I think we should try this again since there was an issue with the
ilmerge that has been fixed now.
On 31 January 2014 11:21, Simon Cropp [email protected] wrote:
@andreasohlund https://github.com/andreasohlund what happens if we only
have symbols for our codebase?Reply to this email directly or view it on GitHubhttps://github.com//issues/53#issuecomment-33750372
.
from nservicebus.
Correct, symbolsource will reject the nuget with a "source files missing"
error
On Fri, Jan 31, 2014 at 1:27 AM, John Simons [email protected]:
It doesn't work because it complaints about not having the source for the
assemblies we ilmerging.
However I think we should try this again since there was an issue with the
ilmerge that has been fixed now.On 31 January 2014 11:21, Simon Cropp [email protected] wrote:
@andreasohlund https://github.com/andreasohlund what happens if we
onlyhave symbols for our codebase?
Reply to this email directly or view it on GitHub<
https://github.com/Particular/NServiceBus/issues/53#issuecomment-33750372>.
Reply to this email directly or view it on GitHubhttps://github.com//issues/53#issuecomment-33750776
.
from nservicebus.
depends on #2200 and #2199 since Symbol Source throws an error for "cant find source" for ilmerged dlls
from nservicebus.
We not doing this
from nservicebus.
Related Issues (20)
- Stream-based data bus implementation HOT 1
- Premature ITransportAddressResolver access corrupts service HOT 1
- AssemblyScanner cannot find concrete serialization types from unobtrusive assembly HOT 14
- It is unnecessarily hard to send messages from recoverability
- Spans and activities on the consumer are not created if the producer does not have OpenTelemetry enabled HOT 12
- ContextPropagation throws an ArgumentNullException when the Activity.Current.Baggage contains a key with value null HOT 4
- Reduce dependencies for net 6 HOT 1
- AssemblyScanner duplicated assembly loading with possible System.IO.FileLoadException: Assembly with same name is already loaded HOT 7
- Allow users to control child trace span creation
- The automatic rate-limiting feature can unknowingly cripple endpoints if there's a bug in the user's system
- Remove polyfil dependencies HOT 3
- For OpenTelemetry metrics, allow Func<string, string> to be specified to trim the enclosed message types tag HOT 6
- Saga and outbox persistence that uses Entity Framework
- Overriding the host name does not work consistently
- AssemblyScanner finds private classes HOT 1
- Obsolete NServiceBus.Logging in favor of Microsoft.Extensions.Logging
- DefineCriticalErrorAction access to IServiceProvider HOT 3
- Support for Azure Event Hubs (Kafka) HOT 1
- Support for Azure Event Grid (MQTT)
- Messages cannot be sent from Windows to Linux using the file share data bus HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from nservicebus.