Buggish: Pasting data from SSMS to Teams Excel (Web)

Issue

When I copy data from SSMS default results table to Teams Excel (Web), data is not translated directly into separate cells.

Cause

The cause for this is due to one of the cells that starts with a single double-quote. This will result with all data after the single double-quote to be in a single cell.

Fix

I do not have a fix for this if you require to keep the double-quote except to manually work around it. This was a data issue on user end which does not resolve the actual issue.

Work-around is perhaps to save the SSMS results in a different format, replace the double-quote with a different value or prepend with an escape character (sorry, I don't know what that is either).

Setup

SQL Server Management Studio	v18.4
Google Chrome	Version 83.0.4103.97 (Official Build) (64-bit)
Teams Excel (Web)	16.0.13014.35904

 

 

Buggish: Visual Studio, "Element [elementName] is not a known element" warning

Visual Studio 2019

I get the errors below randomly. Suddenly while programming the ASP.NET page, my elements will suddenly have the green squiggly warning that my basic ASP elements are not known elements. I have yet to figure out the cause or reason for this to happen, but it does happen somewhat regularly perhaps once a week (of 10-20 hours of programming).

This is purely a syntactical bug, because I can still compile and run my program. It does not interfere with executing the project, but is super distracting. 

My Fix (Updated 9/2/2021)

Issue has increased a bit in the last month but still on the rare side. Fix is still to just close the ASPX page then re-opening. 

My Fix (Updated 4/29/2021)

For the last few months, I found that closing the ASPX page, then re-opening also resolves this issue. This is way faster than my workaround from June.

In the last couple months, I have to say that I haven't noticed this issue. Not sure if maybe I do it so reflexively that I do not notice or that it hasn't happened. I have thought about this until I was skimming over some older posts.

My Fix

1. Clean solution

2. Clean project

3. Restart Visual Studio 2019

I don't know why this fixes the problem. This is my current de facto fix and has worked for the last month. Before that, I some times skipped #1 or #2. Sometimes it worked, sometimes it didn't. Eventually, it just wasn't worth the time to skip one or the other.

• Element [elementName] is not a known element
• Element 'Button' is not a known element. This can occur if there is a compilation error in the Web site, or the web.config file is missing.
• Element 'GridView' is not a known element. This can occur if there is a compilation error in the Web site, or the web.config file is missing.
• Element 'TextBox' is not a known element. This can occur if there is a compilation error in the Web site, or the web.config file is missing.

Reference

Personal experience

My Return to Visual Studio........... sigh

Microsoft Visual Studio

I know in my previous posts that I had left Visual Studio. Sadly I have returned back. In the previous post, I had left primarily through pricing. I was charged a new customer price when I have been paying for over 10 years. My credit card was canceled due to one fraudulent charge, and I did not update my new card with MS. Also shows you how often I use VS, so I just hated that I was practically donating money to MS and they won't even recognize that been blindly paying them for years. Now the company pays for it, so I grudgingly (morally) returned.

Nothing against the actual application, Visual Studio. It is by far superior IDE to the ones I have used in the meantime, including Visual Studio Code. I can only speak for developing in C#, but I have to say that my programming efficiency is noticeably better with Visual Studio. 

Is it worth the cost for a hobbyist? Not really. The main functions are there in free versions, the pain points are tolerable. Is it worth commercially? Yes, the amount of money you save or produce for the company is definitely worth the price. Is the whole Microsoft shop worth it? That is arguable as other enterprise solutions provide a much better price point. If the company is not a technology company, then it is probably worth it. It is a bit bulky, but you don't need the expertise to hire the right person nor pay the additional cost of "real" developers. Not that option is cheap, but my assumption is that non-tech companies will not have good IT and will not have the expertise to really effectively run IT for the long term. They may be able to find one person, but that person will eventually leave or retire, then it will just be downhill. If they are a rare breed with excellent IT, then I recommend that they should consider transforming into a tech company.