The wyDay blog is where you find all the latest news and tips about our existing products and new products to come.
wyDay blog
This little extension automatically installed itself into Firefox when I updated Visual Studio 2008 with SP1. The extension, Microsoft .NET Framework Assistant, describes itself as Adds ClickOnce support and the ability to report installed .NET versions to the web server.:
As you can see the Uninstall button is disabled. I could waste several mouse-scrolls of space bitching about the slimy practice of installing bloat, but I'll just get to the point.
How to uninstall
- Open Regedit (Start > Run > regedit)
- Goto HKEY_LOCAL_MACHINE\SOFTWARE\Mozilla\Firefox\extensions
(or HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Mozilla\Firefox\extensions for 64-bit versions of Windows
- You'll see {20a82645-c095-46ed-80e3-08825760534b}. Right click it and click Delete.
- Restart Firefox.
- Write an angsty live journal entry about why Micro$oft sucks.
Or
- Get back to work.
For more complete instructions on how to completely obliterate this extension from your computer, see the article at annoyances.org.
Subscribe to our blog's RSS Feed or follow Wyatt (CEO of wyDay) on Mastodon (@wyatt@hachyderm.io) to keep up-to-date with our latest posts.
Sweet, thanks!
This thing freaked me out, it's not listed in the FF extensions anywhere and just installs itself, WTF! Thanks.
Hey great job!
I found your solution while getting some info to file a bug.
This issue really pissed me off.
Thanks for the help.
P.S. I found your blog through Google (of course).
That makes .NET developers like me just that little tick harder to deploy any applications for EASY install.
Everyone sees Microsoft and just tries to uninstall. That addon just helps. There are not many ClickOnce apps yet, but it's a nice technology to deploy applications. You won't have to build your own update program (although I did already) and setup. If you don't have Visual Studio Professional it's the only built in possibility.
Stop the MS hate. It makes the life easier mostly. If it weren't for any virus programmer a$$holes, we would have a happy life with our maybe Opera or Mozilla browser, because it's true that IE sometimes doesn't go into standards that much. You can easily lock IE users out by deploying your markup file with the application/xml+xhtml (or was it?) content type. But who would do that? Two negatives by now:
1st: Well, IE still has some good market space
2nd: Every error stops the browser from really interpreting.
I'm going way off. Back to virus programmers. We would still use Active X for active content because it's still the fastest and most flexible technology for internet plugins. Security sucks, which is important today, yeah. But it's the only one where you theoretically could open a DLL file with a full, directly processor run application in it, and it would run fullspeed, not the way slower java stuff, that takes ages to load in a browser, if its something bigger.
Also, clickonce isn't that bad for you. It has some serious security limitations. Like you can ONLY access the IP of the site you DOWNLOADED it from directly with TCP or so clients. That means you cant install some hacking program. It's secure right now. And the little installer doesn't bloat up your Firefox. One addon out of 20 others? Well, thats much on a modern pc, YEAH, it doesnt use up all your memory, maybe 3-4 KB more in Firefox.
I'm a C# developer too. Well, mostly. See wyUpdate, or one of my many open source projects.
Releasing apps is hard, that's just a fact. That goes for any of the .NET languages, C++, Delphi, etc.
I don't hate Microsoft. Why would I? I think you took my joke as a serious statement: "5. Write an angsty live journal entry about why 'Micro$oft' sucks."
Apparently I'm not funny.
I'm not going to comment on this diatribe. Mostly because I don't understand the context.
That's not the point. They installed it without giving me an option. Had they given a way to opt-out then I probably would have just let it install.
I'm fickle like that.
"That makes .NET developers like me just that little tick harder to deploy any applications for EASY install."
Not my problem. Talk to Microsoft about finding a proper solution to this.
My problem is that I have carefully selected the add-ons and permissions of things in my browser for maximum security, specifically so that random people from the Internet can'd just do drive-by installs of stuff I neither want nor need.
And then MS, in an unrelated install (MS Office 2007, thanks for asking), puts in what looks like a honking great security hole right through the middle of this without asking. I've been trying to form a search query on Google for the last 10 minutes, just to find out what this thing is supposed to do, and all I can find is "how to remove it" instructions. That's instructive for me.
One thing I have discovered that it will do is to tell any dodgy website advertisement exactly what variant of .NET framework I am running, so that they can target the precise security exploits exposed in that version.
Aha, do a search with "ClickOnce"...
"Hence when a user clicks on a .application in IE our mime handler is invoked which downlods the .application file and fires up the ClickOnce install." Sounds like a way to download and execute arbitrary code to me. Great.
Smashing. It's straight coming off as soon as this installer finishes.
It seems there's a lot of anger here. And a lot of misunderstanding.
I don't like ClickOnce or this extension, but neither are arbitrary code execution. Sure, this extension adds extra junk like the .NET version string to user agent, but extra bloat does not equal a security hole.
I think the problem we're having is lack of permission. They didn't get our permission to install the extension, thus the failed humor in my case and the slightly angry rant in yours.
Maybe it was an intentional breach of trust on Microsoft's part. More likely it was just an oversight - a forgotten option in an installer.
Either way, lets keep this conversation civil.
Hi,
I had a Java extension as well. It seems to me that the real problem is Firefox. It shouldn't let the uninstall button be disabled under any circumstances, and really should let anything be installed without user permission.
I'll start with this point. Firefox has no control over how the user modifies the program. If I wanted to overwrite the firefox.exe with all 0's, Firefox wouldn't be able to stop me.
Similarly, I can install any extension I want when Firefox is not running - it won't be able to stop me. Even if Firefox were to add extra checks, I can just find and bypass those checks.
The uninstall button being disabled is a Windows user permission problem (limited-user vs. admin-user vs. admin-user with UAC enabled).
Since the extensions (Java and this .NET extension) are being installed on a system-wide level, they have to be removed on a system-wide level. That is, it's more complicated than just enabling the Uninstall button. This is especially true since Firefox is run at the user-level, and it may or may not be able to delete Registry keys in the HKLM tree (depending on the user's permission & whether UAC is enabled).
I don't believe it's due to permission problems or UAC as this also occurs in Windows XP for the Administrator user. It just seems like a bug to me. The user should be able to disable an add-on/extension no matter where it be, at least in my opinion.
Thanks for the info, though. I just simply didn't want or need the add-on, and I'm generally against programs installing things without asking. Off-topic: I mean honestly, why must programs litter my desktop, quick launch toolbar (which I don't use), and nicely organized start menu with their icons? At least let me specify where in the start menu.
It's the usual arrogance from Microsoft. "Oh, we know what's best for you, so we'll just install this for you and not let you uninstall it."
I use Microsoft's crap because I have to, not because I want to, and it's this kind of thing that makes me very much not want to.
And for those of you who think it's a great idea, bear in mind that it's my computer and that I have it set up to run the way I want it to run. Tinkering with that setup is my business, not Microsoft's and not yours.
The user agent may still be set after the addon is disabled or removed. Use about:config to search for .net and reset the key.
I'm certainly not a "Microsoft hater" (why would I use Visual Studio if I were), but any code that just insalls itself without asking for my permission first (and explaining what it does *beforehand*) is just a no-no.
But even now I don't actually see what this extension does for me. Just installing it "because it's from Microsoft, and Microsoft knows what is good for you" doesn't sound like a good idea.
So I will disable it now. And if somebody comes up with a very good argument why this is something I really must have, I can always re-enable it.
The whole point of firefox is to get you control over what is happening on your machine.
Microsoft didn't miss that point.
It ignored it.
If it had been published with the rest of the addons
with a explanation of what it does, and why one might want it,
just like the rest of the world does,
it would have received a much different reception.
At the same time .NET Framework Assistant was installed as an Addon I got the "Ask" search engine addon. Sure I can disable these - but it distrupts my "neat and orderly" list of extensions. I will be editing my registry to get rid of it (the .NET) as suggested previously - the "Ask" search feature I was able to uninstall.
It is my computer. Any company that ignores that gets cursed during the time I have to use to search the internet to see how to deal with a new situation that crept, and the time I have to spend to do the removal work. What does Microsoft (or any other such company) expect?
Meanwhile I don't hate the company - I use several of their products. But it does make me eager to switch to another company's application the moment one becomes available that does a comparable job.
Well, it came late to me (maybe while I'm german?), but it got me at last..
Yes, we bought the machines, we paid for them, for those progs,
we use and have to work with - but in no way they are our computers, our progs.
We only describe as "holders", I'm using the straight translation for the german "Besitzer", which is not correlate to "owner"...
those real proprietaries can and do what they want to do. Unspecific
claims are to be read in every "EULA", the big and not so big companies are shippin',
isn't it?! So, no one of those (BB's) should be mourning about bad reputation, as long as they're playing cards off the table.
No offence!
dierk
dierk,
I have no idea what you're talking about. This issue has little to do with the legal necessity of EULA, but rather permission to install extensions.
Legal issues ? Permission issues
JTimouri,
That's a bit extreme.
I bookmarked this tip when I had to use it and it's just come in handy again. The new version of Nokia PC Suite forcibly installs a bookmark syncing extension which can't be uninstalled in the usual manner. Very useful blog post, thanks!
Microsoft just installed a piece of their software into a firefox installation without asking my permission. they clearly did this intentionally, thus forcing their code into my third party software installation. microsoft just came into my house, installed a new door in my living room wall, and they even tell me it is not possible to be removed. this is like raping somebody and then telling the victimized person: "it's better for you". what is going to be next: ERASING firefox? or erasing other software?
microsoft announced this as a patch for NET, and nowhere in the documentation about the patch is there any word to be found of microsoft intstalling software into my firefox.
What is TRULY infuriating is that unlike any other add-on, it cannot be uninstalled directly from Firefox. I like the analogy of an unsolicited installation into your house, and then forcible prevention of your trying to remove it.
IMHO, this is NO DIFFERENT than the worst kind of spyware installation, and should be reported as such to the appropriate security watchdogs.
GK
It is BIG impertinence !!!
I get this "junk" from regular windows update. It did not ask me if I want it! It cannot be uninstaled by the standard way!.... Thats why Micro$oft sucks.
I hope the developer, who decided to install a plugin in FF, will ne fired soon. This is not a got marketing action to install anything within a non microsoft application. Further more, not to allow to uninstall it. Blame on you, M$.
I just installed Java JRE 6.0 Update 11. They are doing the same shit as M$. Firefox told me, that two new addons were installed. One of them I could find (Java Quick Starter), which could not be removed within FF, but only in the Java Control. The second addon is not visible or I even could not find it.
Please, you software developer, please let ME decide, which software will be useful for me. I don't need your help!
I don't understand why you would want to hack the registry. Just disable the extension; it has exactly the same effect, surely?
just got this today ... I think it must have come w/ my important windows updates
thanks for helping me remove it!
btw, I dont have a problem w/ MS but I do not like things mysteriously appearing on my laptop & then have the "uninstall" option grayed out.
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Mozilla\Firefox\extensions
Then the rest for those of us running in a X64 environment.
Thanks Mashiki, I've added it to the post.
hello i did a system restore to the last check point it took out the ff extention....
Blake, you just rolled back a Windows Update. The Firefox extension will come back the next time Windows automatically updates.
If you want to remove it permanently then you need to follow my procedure.
thanks is this update neccessary.... i usually turn off automatic updates...
Wyatt, I think "permanently" is a little strong. I expect that the registry entry will be recreated whenever the .NET framework gets repaired ... this could happen for any number of reasons, but is particularly likely each time it gets updated.
I still don't understand why you don't just disable the extension. That makes sure Firefox won't load it, without having to hack about in the registry. Is it that big a deal to have this extension appear in the list? Or is there some other issue I'm missing?
I've never had to repair the .NET framework installation, but you're right - it'll reinstall the extension when repaired.
The reason I wanted to remove it is because there is a cost associated with loading extensions. Nothing is free - that is, nothing take 0 time to load.
Sure, a few milliseconds is barely perceptible, but why waste time on something I don't need? Plus, the uninstall button being disabled irked me (but it turns out that's actually a Firefox problem).
It seems that disabling it doesn't completely stop the changes it made. If you check your useragent string after disabling it it still has "(.NET CLR 3.5.30729)".
Installs without concent, invokes IE when you click the relevant links, cannot uninstall it (easily) and disabling it does not completely undo the changes it makes.
Thanks a lot microsoft.
Official edict from ruler of the universe, Wyatt O'Day
All new comments must be in one of the following forms:
Form 1: A haiku.
Form 2: One witty, well edited sentence.
Form 3: A solution to the problem (i.e. not "Ubuntu is awesome lol rofl bbq omg imho")
All other comments will be deleted. (7 offenders so far)
"Windows updates ready?"
You sneaky little bastards!
Out, you damned crapware!
"All your base are ours!"
No, all my base are MINE, jerks!
F***ing Micro$oft...
Wave "bye, bye" Window$..
Say "hello" to Ubuntu.
Ahhh.. that's MUCH better!
Windows updates hell?
Hehe.. Glad I'm on a Mac.
MY Firefox is fine!
Firefox v. Windows
Plenty of blame to go 'round
It's winner takes none.
Micro$oft screwed you..
How would New Yorkers respond?
"F*** you f***ing f***s!"
They insist you lose.
Bend like a reed in the wind:
They lose you to GNU.
microsoft installs
dot NET framework assistant
without asking me
You do not ask
if you are afraid
of the answer
This is exactly the reason why it's easier to just install it and why we will never experience democracy in the 'free world' - people aren't informed enough to make the right choice.
I also do some .NET development. Take a leaf out of the linux book, and ask... Ubuntu asks when it installs it's own extensions into firefox. Also, take another leaf from that world and understand making distribution easier at the consumers expense is no the way to go.
Also for full delete, remove registry key mentioned above, delete "DotNetAssistantExtension" directory from "C:\WINDOWS\Microsoft.NET\Framework\v3.5\Windows Presentation Foundation\" and modify your prefs.js to set user agent string back.
Oh, and btw. Firefox has to check every extension see if it's enabled or disabled, then load it if it's enabled every start. Extensions therefore slow down firefox starts and consume resources (less so if disabled but still happens).
Just for reference here is Microsoft's MSDN page that describes this little beasty:
http://msdn.microsoft.com/en-us/library/cc716877.aspx
Abusive language doesnt make the language bad
Same goes for bad programmers/programming doesnt make .net bad!!
Speak for yourself - You are NOT talking for the .net community when you say hey MS made it so its good to be good/bad.
be an adult and realize that the world is NOT full of idiots who want decisions to be made for you - Be Upfront!
Its folks like you that end up giving Microsoft (or any Corporate) a bad name.... you possible have nothing to do with them more than a passing fancy to call yourself a programmer
Be Civic!
Wyatt - Fantastic job. Its appalling when you goog and cant find a thing about it - supposed to be an addon but no information is listed on FF's addon site
Gaspard - Thanks
Funny Freudian slip - that MS programming guy writes:
"Everyone sees Microsoft and just tries to uninstall. That addon just helps."
Unwittingly, he got *that* right - drive-by installs with disabled uninstalls don't "just help" faster app deployment - but they DO "just help" people hate MS even more...
Thank you for this blog!
=====
I have a comment about a previous comment:
>> Oh lord. - November 7th, 2008 at 3:02 pm
>> Everyone sees Microsoft and just tries to uninstall...
>> Stop the MS hate. It makes the life easier mostly.
Boy, are you hopeless - however - I will give you a short (three step!) guide to understanding:
1 - Microcrap sticks their crap onto my computer.
2 - My computer belongs to me - not to microcrap.
3 - Microcrap makes it hard for me to get rid of their crap. This is a perfect example. In fact - an ordinary user is left with Microcrap on their computer that they can't remove.
Really - it's not hard to understand the problem. Not at all.
whoops - I didn't see this...
>> Form 1: A haiku.
>> Form 2: One witty, well edited sentence.
>> Form 3: A solution to the problem (i.e. not Ubuntu is awesome lol rofl bbq omg imho)
>>
>> All other comments will be deleted. (4 offenders so far)
#1 - I can't think of one.
#2 - Explaining the problem in a single sentence - I don't think that's possible.
#3 - Well, installing unix is a solution.
Hmmm...
Installing unix
stops microcrap infecting
your reality
Well, thank you MSoft developers for another reason on my list of things why vista is my last MS OS. You sure make it a long list.
First you use WGA which treats ppl like criminals for trying to update security on their BOUGHT system.
Then you create UAC which tells us users how to run our computers.
And now you install add-ons in our non msoft browsers. Talk about invasion of privacy. You have no right to install anything on our computers without our permission with as little right as we have to download and install a security update from msoft without a proper wga.
And to me anything installed without my permission and without a proper uninstaller is considered spyware or malware. And thus being removed without problems!!!
@Oh lord
It's not the fact that it's Microsoft that makes me want to remove it, it's the fact that this is installed, without any removal functionality without user consent.
Microsoft fans remind me of republican voters. Actually ready to argue that this kind of practice is not only acceptable but really good.
I am a republican, and I usually feel the democrats have the "it's not only acceptable, but really good" mentality. In a bi-partisan move; let us agree we both feel this way about Microsoft.
Installation without authorization, .NET was allowed, but they over stepped the permission they were given, and no un-install option. Even if the un-install problem lies in FF itself, MS deployed an un-installable add-on. They took the time to make the add-on, but not the time to properly field test or support. So regardless where the root cause is, MS allowed it to propagate.
Has anyone mentioned FFClickOnce? It's is a third-party Firefox extension that also enables ClickOnce for client installations that have Firefox plus .NET Framework
Wyatt ... just to say thank you for the uninstall information.
thanks
Thanks a lot, Pete! Solved the answer at one go. I dream of the day robots take over the world and, as their first act of imperial government, outlaw Windows. Except for use at Redmond, where it will be mandatory. And in hell, of course. But that goes without saying.
I meant thanks to Wyatt. Sorry. Pete was the bloke who sent me the link.
Thanks a lot, Wyatt. Not only was this the location for the .NET issue, but the Java Quick Start was also there. I deleted both registry entries and VOILA, no more .NET or JQS.
Thanks! I already deleted this once but once again the MS "important" updates put it back.
Thank you for posting this — HUGE help!!!
Thanks for this useful tip!
Back to work now :)
No one understands my pain... oh wait, wrong page.
Thx for the tip Wyatt.
That the uninstall is disabled is coming from Firefox.
The extensions are installed outside of Firefox and without the control of Firefox and Firefox simple can not uninstall such extensions because Firefox doesn't know where files are dropped by the installer. The external addon installer could for example put files in the Firefox directory. That's the reason why extensions installed with the registry are not uninstallable inside Firefox.
The point is that every external extension installer should ask before installing and don't do that silent.
Apparetly, a few more steps are required to really uninstall the plugin—-see http://www.annoyances.org/exec/show/article08-600
Thanks ander, I've added it to the main post.
I think the question is: why the heck does Mozilla allow for extensions being installed outside Firefox's control? do they want to repeat MS's past mistakes regarding browser security?
Hmmmm The government pushed out this patch and installed this "freak" of a thing on my machine at work. Can't remove it without admin privs (can't edit the registry).
What does this do exactly? I can't find much other than "it shouldn't be there", "opens up Firefox for attacks" - things like that. No specifics.
Any other way to remove it than registry?
RickX,
It's not malicious, despite what the multitude of imbeciles might suggest. If you can't remove it, it's no biggie.
All it does is waste a little bit of time on Firefox startup. You can solve this problem by getting the gov to buy you a better computer.
- Wyatt
Hmm, that's weird, my uninstall button was working.
Running Firefox 3.0.10 on Windows 7 RC (x86)
Thanks for the help.
@Michael The reason your Uninstall button is working is due to an update to the actual extension from Microsoft. If you don't have the update, only the Enable/Disable button should be functional for stopping the extension from doing whatever it is programmed to do.
The update can be obtained here:
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=cecc62dc-96a7-4657-af91-6383ba034eab
The fun part is that since the update is installed outside of the normal add-on mechanism for Firefox, you can't get the update via the add-on update check.
This is why people should work within the accepted system instead of just auto installing software (plugins, extensions, applications, etc.) automagically.
Apple has been pinged on this with regards to Safari, Apple Update, and Bonjour for Windows.
Andy
Hanselman has a good write-up on this.
http://www.hanselman.com/blog/HowToRemoveTheNETClickOnceFirefoxExtension.aspx
On a positive note, it is incompatible (at least for now) with the new Firefox 3.5 so FF mercifully disables the add-on for you.
http://support.microsoft.com/kb/963707
Thanks a lot Wyatt - nice try from MS to make people return to IE
For crying out loud. This has nothing to do with IE. And, when things are done in the proper order, everything works and the Enable / Disable / Uninstall buttons work just fine.
It is the sequence of updates that eludes most of you apparently.
The original .NET Framework 3.5 SP1 update is NOT compatible with Firefox. M$ says this if you read - RIF - the KB article that goes with it.
That is why they released a separate .NET 3.5 Framework Assistant SP1 update JUST FOR Firefox users. They did NOT have to do that. In fact, NOT doing so would force users back to IE, eh Marthin!
Here's the rub. The .NET Framework 3.5 SP1 update installs Framework Assistant 1.0. Version 1.0 is ONLY compatible with Firefox 3.0.x (NOT 3.5.x). So the .NET Framework Assistant 1.1 update cannot update an existing FF 3.5.x installation because the Framework Assistant is not enabled.
HOWEVER, if one is still using FF 3.0.x, one may proceed to install the .NET Framework 3.5 SP1 update, ensure that Framework Assistant 1.0 is enabled in the FF addon list, then install the Framework Assistant update to 1.1. THEN one can update to FF 3.5.x and all is well.
I know. I did it last night on the backup XP MCE machine and it worked faultlessly.
Now before all you MAC / Unix / Linux / etc fanboys get on my case, I don't think anyone who follows my pitifully few postings would ever even consider calling me a M$ supporter. In fact I think the way Bill uses his monopoly borders on criminal (and some folks in the EU agree). BUT the fact that it works if one follows the specified order of events shows that M$ was at least thinking about how to accommodate FF.
Anyhow, y'all can rant and rave about .NET (I know I hated what they did to VB6) but if someone writes a program in .NET and you want to run it, guess what! You gotta have it. And whatever it is that Assistant does is likely to be required by application developers for something down the road (if not now) or M$ would not have bothered spending money on it. Remember they are in the business of making money.
Now I'm getting back to my original question: if one has already upgraded to FF 3.5.x, how does one get .NET Framework Assistant 1.1 installed properly since version 1.0 cannot be enabled in FF 3.5.x!!
Jim—have you tried the update found at:
http://www.microsoft.com/downloads/details.aspx?FamilyID=cecc62dc-96a7-4657-af91-6383ba034eab&displaylang=en
I'm writing this pretty much after my firefox warned me about this add-on and advised me to disable it. I did, and then i successfully uninstalled this add-on from firefox. the Button wasn't greyed out. should i be worried about it coming back on it own? (Like some kinds malware that we've heard about)
The button wasn't greyed because MS got their act together and fixed the bug.
No.
A lot of people contributing to this thread are asking why they should disable .NET Framework Assistant? What harm is it causing Firefox. Well here is a possible answer. And Firefox today automatically disabled .NFA and WPF!
Battle of the Softwares: Microsoft vs Mozilla Firefox!
nice work dude
thanks for uninstal netfrmework ..great..firefox will be faster..
That was easy! Thanks for that fix, Wyatt. I was sitting here cursing Microsoft for automatically sneaking another useless file into my machine, and found your blog. I'm glad I found you.
xox
Ellen
No problem at all, I'm glad I could help.
Thank you thank you thank you... you just made my day.
Thanks for the information. I been trying for months to get ride of this pesky idiot add-on from Microsoft.
Once again, thanks for the info.
Imagine half-ass installing a software or two on your personal computer and it's trying to boot up with Windows. What do you think will happen? What's likely to happen is...your system becomes unstable and crash with a B.S.O.D.
My FF 3.6.3 started crashing recently for no reason and when I looked at it's installed plug-ins I found out that Microsoft Net Framework Assistant 1.0 plug-in was grayed out. When restarting FF from previous before crash, I ran about 15 attempts at re-loading the plug-in's website and it caused FF to crash while loading. After removal, FF is running smoother without crashing.
I wouldn't suggest that any half ass installs as being safe. Call me paranoid if you like but, if it's not installed correctly folks, then get it off of your system. Best to be safe than sorry.
A great big THANK YOU!!! goes out to Wyatt from me.
As an extension developer, how can you grey out "disable/uninstall" buttons?
If you've gleaned anything from this article it's that you absolutely should not emulate this behavior.
I really like your writing style, good info, thanks for putting up :D. "Much unhappiness has come into the world because of bewilderment and things left unsaid." by Feodor Mikhailovich Dostoyevsky.
I'm still learning from you, while I'm trying to achieve my goals. I definitely love reading everything that is written on your blog.Keep the information coming. I loved it!
Simply Awsome post !
This blog was... how do I say it? Relevant!!
Finally I've found something which helped me. Thank you!