It's also a clash of languages I think. The snippets coming with C# are very rudimentary, stored in a single folder and simply contain very often used constructs. The snippets for VB.NET however are grouped in various folders, and often contain code you type in without thinking (IMHO), though there's a snippet for it
.
What I'm getting at is: if I provide a 10, 15 line snippet it might be worth it, but if it requires you to remove at least 7 lines it's not that worth it.
Writing them is pretty low level, but it's ok
I've now: (and I'm adding way more, the categorization of VB.NET is actually good, good idea Omar to bring that up
)
- adding using / Imports to the code file (adapter/selfservicing)
- creating an entity collection (adapter). The selfservicing one is such a no-brainer, it takes more time to find the snippet than to type it in.
- defining a using(DataAccessAdapter $adapter$ = new DataAccessAdapter()) { } block (also in VB) (adapter)
- defining a 1 node prefetch path (adapter, selfservicing)
working on more
The general shortcuts I use are:
llblA__name_ for adapter stuff and
llblS__name_ for selfservicing stuff.