Skip to main content

Reshuffler International

Having a new director does not ensure easy transition. After a few reshuffling in the structure and organization in my university we had the biggest surprise. We have anew boss, because our old boss was transferred to another assignment and the new boss is and eversince she is a BOSS. She occupies a very high position in the university  structure and now she on us..wow.. Pressures were felt as she conducted the first meeting with us. Reality Bites!!!

Its the last few days of June again we still havent deployed anything from the newly developed IS and i starting to worry.. If the schedule is to be met the deployment should have started but because some things are still to be resolved , we have to wait again.. Regarding my problem on ClickOnce well until now it is still a problem but im having great developments on it..keep u posted on that....

Right now my fellow faculty is in the seminar hall listening to Dr. Lourdes Quisumbings talk and im here fiddling with the keyboard....Lucky for me i have to look into the installation of the PABX systemin the school.. Ill surely miss a great talk but ill be there this afternoon..

Knowledge seem to come from anywhere so dont stop learning and dont stop evolving.......    

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

renaming default namespaces for VSTO projects in VS2008

So here is the scenario , you are starting a VSTO project and decided that your default namespace is ExcelAddInTesterApp . You created the project and started coding the project. After several days , your boss called and said "hey marvin , make use of this namespace OurCompany.ExcelAddInTesterApp , we have to add our company name to it got it?" . You get back to your machine thinking its just a simple property just like any project you've been working on. So you right clicked the VSTO project and hit properties . Boom! What the F@#$? The default namespace textbox is disabled!!!!



I've been through this and I googled for ways to do it and ended up with a blog from a Microsoft MVP telling me it can't be done because it is disabled. Then I thought of Refactoring, the beauty and grandeur of the renaming process. I selected the namespace and hit the refactor menu hoping that this would solve the problem . Unfortunately , it did not rather it displayed the message box …

Automatic Properties and Object Initializers in .Net 3.5

With the release of .Net 3.5 alongside with Visual Studio 2008 , new enhancements was again introduced . Some maybe well pronounced such as the inclusion of WCF, WPF , LINQ in .Net 3.0 and some just came unnoticed. If you have been accustomed of using a particular method or technique in implementing a certain code in .Net 2.0 , because of backward compatibility , you may not even notice that there are new ways of implementing it in .Net 3.5.

Here are two new concepts in .Net 3.5 that a developer may not notice ( at least in my opinion ) : Automatic Properties and Object Initializers . To illustrate these two , I am going to present the pre-.Net 3.5 way (.Net 2.0) and the .Net 3.5 way in creating a simple class with simple properties.

Automatic Properties

Creating a class can be tedious , especially when working with a list of properties , . One way to get around having to type the code for a private field and its public property getter and setter is to use a refactoring tool. However, …