Skip to main content

On Visual Studio 2005 Beta 2

Microsofts ever anticipated release of visual studio 2005 is long overdue. I startedformally the universitys student information system january this year with two possible options . First was the use of Visual Studio 2003 trial edition (good for 60 days) and the other was using the Visual Studio 2005 beta 1 Whidbey. Knowing the fact that VS2005 will be released soon , i ventured on the use of beta 1. It was reallya very bumpy ride, the application was a source hog, i need to upgrade my pc just to keep it running. It featured a nice interface and development tool though. It was all fine, having a good IDE , new controls , good debugging tools, crystal reports ..all the goodies a programmer might ask..then it expried!!!!

Well , we tried to expreriment on other options just to keep beta 1 alive but , unfortunately i was time to go... im almost through with the development!!!!

i downloaded beta 2 express edition , i dont have any MSDN subscription to download the standard beta 2.. the IDE improved , except taht there are something s that i can do in beta1 which i can no longer do in beta 2!!!!!! express edition!!!!!! at least i have made the ClickOnce technology work..yes it worked for christ sake!!

the school have the money , microsoft dont have the goody!!!!! i just hope it ll be out soon!!!

Comments

Popular posts from this blog

Hiding Unwanted Python Folders and Files in Visual Studio Code

Visual Studio Code is a universal editor and pretty good at it. However, the explorer view maybe cluttered with the automatically generated folders and files confusing developers. Python is no different. Below are example files and folders generated by Python.

The __pycache__ folder and *.pyc files  are totally unnecessary to the developer. To hide these files from the explorer view, we need to edit the settings.json for VSCode. Add the folder and the files as shown below:
Copy and paste the lines below :

"**/*.pyc":{"when":"$(basename).py"},"**/__pycache__":true

Getting Started with Stateless : A Lightweight Workflow Library Alternative for .NET

A year ago, I was looking for a simple workflow manager for a project I was working. Its a medium sized application that involves tracking the state of assets in the system. Back in 2008, Microsoft (MS) introduced new technologies along with the release of Visual Studio 2008: Windows Presentation Foundation (WPF), Windows Communication Foundation (WCF), and Windows Workflow Foundation(WF). Having worked in a company utilizing mostly MS products for development, my first option was to go with WF. After doing some time reading and studying the library, I paused and decided it was too complex for my requirement. Using WF would be an overkill and the fact that it has, a rather, steep learning curve, there has to be another option. My mind toyed with the idea of developing a simple workflow library myself. It would be a learning experience but it might end up consuming a lot of time.

Why reinvent the wheel? So I started querying the internet for a better solution. I stumbled upon Stateless

Get Started with MongoDB Stitch : The New Backend As Service Offering from MongoDB

Halfway of this year, the guys from MongoDB launch their new backend as service product called MongoDB Stitch. While the launch is just for the beta, the promise of the service is quite interesting. MongoDB has been around for long now and some development stacks have been based on its database product, the MongoDB-ExpressJS-Angular-NodeJS (MEAN) and the MongoDB-ExpressJS-React-NodeJS (MERN) stacks to name a few. These stacks, however, relies on backend technology such as ExpressJS and NodeJS. The idea of provisioning servers and developing the backend solution makes it daunting for small to medium scale applications. MongoDB Atlas, at least made life much easier by providing on cloud database solution, but there must be a simpler solution, right? A solution the would stitch the backend and frontend together ( see what I did there ?).
MongoDB Stitch lets developers focus on building applications rather than on managing data manipulation code, service integration, or backend infrastruct…