Skip to main content
replaced http://stackoverflow.com/ with https://stackoverflow.com/
Source Link

Quite impressive - am looking forward for more!

I'm afraid you'll need to change the library name soon though, as LINQToStackOverflow is at odds with the recently published Trademark GuidanceTrademark Guidance, which explicitly asks for only one of the terms, "Stack" or "Exchange" or "Overflow" in your product name.

So may I suggest the obvious: LINQ to Stack ;)

Sounds pretty cool to me and I'd presume the term 'Stack' in itself ranking high SEO wise soon regarding the Stack Exchange sites, despite its generality, and even more so for developer oriented stuff like yours.

Quite impressive - am looking forward for more!

I'm afraid you'll need to change the library name soon though, as LINQToStackOverflow is at odds with the recently published Trademark Guidance, which explicitly asks for only one of the terms, "Stack" or "Exchange" or "Overflow" in your product name.

So may I suggest the obvious: LINQ to Stack ;)

Sounds pretty cool to me and I'd presume the term 'Stack' in itself ranking high SEO wise soon regarding the Stack Exchange sites, despite its generality, and even more so for developer oriented stuff like yours.

Quite impressive - am looking forward for more!

I'm afraid you'll need to change the library name soon though, as LINQToStackOverflow is at odds with the recently published Trademark Guidance, which explicitly asks for only one of the terms, "Stack" or "Exchange" or "Overflow" in your product name.

So may I suggest the obvious: LINQ to Stack ;)

Sounds pretty cool to me and I'd presume the term 'Stack' in itself ranking high SEO wise soon regarding the Stack Exchange sites, despite its generality, and even more so for developer oriented stuff like yours.

Added (former) library name to preserve context.
Source Link
Steffen Opel
  • 1.4k
  • 8
  • 14

Quite impressive - am looking forward for more!

I'm afraid you'll need to change the library name soon though, as yoursLINQToStackOverflow is at odds with the recently published Trademark Guidance, which explicitly asks for only one of the terms, "Stack" or "Exchange" or "Overflow" in your product name.

So may I suggest the obvious: LINQ to Stack ;)

Sounds pretty cool to me and I'd presume the term 'Stack' in itself ranking high SEO wise soon regarding the Stack Exchange sites, despite its generality, and even more so for developer oriented stuff like yours.

Quite impressive - am looking forward for more!

I'm afraid you'll need to change the library name soon though, as yours is at odds with the recently published Trademark Guidance, which explicitly asks for only one of the terms, "Stack" or "Exchange" or "Overflow" in your product name.

So may I suggest the obvious: LINQ to Stack ;)

Sounds pretty cool to me and I'd presume the term 'Stack' in itself ranking high SEO wise soon regarding the Stack Exchange sites, despite its generality, and even more so for developer oriented stuff like yours.

Quite impressive - am looking forward for more!

I'm afraid you'll need to change the library name soon though, as LINQToStackOverflow is at odds with the recently published Trademark Guidance, which explicitly asks for only one of the terms, "Stack" or "Exchange" or "Overflow" in your product name.

So may I suggest the obvious: LINQ to Stack ;)

Sounds pretty cool to me and I'd presume the term 'Stack' in itself ranking high SEO wise soon regarding the Stack Exchange sites, despite its generality, and even more so for developer oriented stuff like yours.

Source Link
Steffen Opel
  • 1.4k
  • 8
  • 14

Quite impressive - am looking forward for more!

I'm afraid you'll need to change the library name soon though, as yours is at odds with the recently published Trademark Guidance, which explicitly asks for only one of the terms, "Stack" or "Exchange" or "Overflow" in your product name.

So may I suggest the obvious: LINQ to Stack ;)

Sounds pretty cool to me and I'd presume the term 'Stack' in itself ranking high SEO wise soon regarding the Stack Exchange sites, despite its generality, and even more so for developer oriented stuff like yours.