I finally setup my blog at WebLogs@asp.net
Check it out
No more posts here. Thanks to the DotNetJunkies for hosting my Blog these months.
Just got this error message from Firefox advising me to restart... Navigator!!!
You can't eliminate problems, but you can make trades to get problems that you prefer over the ones you have now.
Taken from an Eric's post.
Mike Krueger has created a .net wrapper for libusb library.
Good News! My MSN.com e-mail account was upgraded, 250MB of space!!! but my main hotmail.com account hasn't been upgraded, hope it gets the upgrade before end of the year.
I need to UnRegAsm and Delete an Assembly in the same .net program. UnRegAsm'ing is easy, just use the method 'UnregisterAssembly' from class 'System.Runtime.InteropServices.RegistrationServices'.
But to use 'UnregisterAssembly' method you need to load the Assembly to be unregistered and when trying to delete the assembly using 'System.IO.File.Delete' I get the error:
Access to the path "..\MyAssembly.dll" is denied.
Researching the problem I read in the web that a loaded Assembly is not released until its application ends. Is there a way to 'manually' release the assembly ?
I've read something about creating another AppDomain but it seems very
complicated...
Could somebody help me ?
On Monday I got a new hp/Compaq PC and it included a 5500 monitor configured
at resolution 1024x768, after an hour of using the new monitor my eyes started
to itch and an hour later they turned red.
I check the display configuration and noticed that the refresh rate was set
to 60Hz, at first I was blaming the tech support guys for configuring such low
refresh rate but when trying to change it to an upper value I get a message from
the monitor saying that it doesn't support refresh rates greater than 60Hz for
that resolution.
60Hz!!!! Does hp/compaq also sell this s***t monitor in USA ? or only in third
world countries (like Peru where I live) ?
I talk to the tech support guys and they're right now changing my monitor
back to my old IBM E54 wich at least supports 75Hz at 1024x768, I think I will
have to spend my own money to get a good monitor. My eyes will thank me.
Follow these
instructions from Trev:
OK, how to repair a copy
of MDAC 2.8 on WinXP with SP2 installed
first, locate the mdac.inf file in c:\windows\inf right click and install
when prompted for a location, point to
"c:/windows/servicepackfiles/i386" then when prompted for the XPcd,
either load the cd or point to c:\i386
hey presto, this reinstalls / repairs MDAC 2.8
It solved my
problem when using ADODB objects from .net, thanks Trev!
I wasn't the only one
with problems with MDAC after installing WindowsXP SP2..
I'm creating a .net library (based on the code of
an article written by Bill
Vaugh) to convert ADO.net Datatables y Datasets to ADODB.Recordsets.
Yesterday I got a new dev machine with WinXP-SP2 to replace my old Win2000-SP4
and now when I try to use an instance of an ADODB.Recordset object in my code I
get the error "QueryInterface for interface ADODB._Recordset failed".
Dim
rsResult As
ADODB.Recordset = New
ADODB.Recordset
rsResult.Open()
Even worse I have tested the executable, compiled in my PC, on two others PCs:
1 with Windows2000 Server SP4 with MDAC 2.8 & net v1.1
1 with WindowsXP Pro SP1 with MDAC 2.8 & net v1.1
and it runs just fine in both of them.
Could MDAC 2.81 included with WinXP SP2 be blamed for this error?
In my VBnet project I'm referecencing to "C:/Program files/Microsoft.NET/Primary Interop Assemblies/adodb.dll"
Hope somebody could help me....
I just got my new office PC loaded with Windows XP SP2 and since the tech
support guys don't install IIS by default in XP PCs I will take a WindowsXP CD (the
original release *not* slipstreamed with any service pack) and install IIS, but I
was thinking about the patches and imporvements for IIS that SP2 contains.
Anybody knows if I DO have to re-install SP2 after installing IIS ???
I missed the release of the new version of the SAP .net connector, if you have an OSS user you can get it SAP web site : http://service.sap.com/connectors
from the release notes:
2. What is New
=============
2.1 Runtime
===========
- The old SAP.Connector assembly was split into two assemblies. The new
SAP.Connector assembly is now free of unsafe code
and can be used in partial trusted environments.
- Support for ".NET Remoting".
- New unified connection management for both Rfc and Soap connections.
- Improved "Destination" classes, for example new "Properties" for Soap support,
for SAPRouter strings and the new "CombinedDestination"
and "ConfigDestination" classes.
- Improved connection pool allows, for example, the limitation of active
connections.
- Support for RFC callbacks
2.2 Design Time
===============
- Full Visual Basic © support. All proxies can be created in both C# and VB. All
other languages are still supported via language interoperability.
- Full BAPI/Business Object Repository support, including keyfields, parameter
renaming/reordering and more.
- New "Server Explorer" extension: The SAP Proxy Wizard was replaced by an
extended designer and an extension to "Server
Explorer" that allows you to drag and drop all required functions and objects.
- "Smart Typed Dataset" feature of proxies allows you to have state in proxies
and data-bind to user defined proxy fields.
- "Connection wiring" allows you to define the used SAP connection with a few
mouse clicks.
- XML comments are generated with the proxy generator for the use with
IntelliSense help and external documentation tools.
2.3 Documentation / Samples
===========================
- The Documentation is integrated in the Visual Studio Help.
- IntelliSense Help is available for all classes, methods and parameters.
If your page/site doesn't show up in the result of the new MSN search (still in beta) you can
submit it to MSN.
Fact:
If you type "w" and then press [Enter] in the Address bar in Firefox it takes you to http://www.georgewbush.com
Conspiracy theory:
so it seems the 250,000 bucks Firefox has collected came from Republican Party funds.
Before the flames start this hole post is a joke... ;-)
Truth:
Firefox takes you to the first site that a Google search for "w" returns and these days the most famous site with "w" seems to be Bush's.
Just found another peruvian .net blogger. His name is Guino Henostroza, he's a C# MVP.
This reminds me that I never posted an introductory post with info about myself (like the fact of been from Peru), added to the to-do list. ;-)
"You may have heard about the MSN Messenger Beta that some people are trying out. You’ll be able to try it out soon too!"
You can subscribe for an alert here.
Meet Bob's dog!
Check this Ben's post and this page for more info about Rover!
Microsoft has released Photo Story v3, and now it's free!!!
Read Paul Thurrot's review.
great news!
Taken from Web Q&A column of the November 2004 MSDN Magazine edition:
Unless you are hosting the WebBrowser control, you can't effectively stop the use of the Back button. See Knowledge Base article 811603 (''Use the Forward Button and the Back Button for WebBrowser Control in Visual Basic .NET'') if you need more info on using the control.
You can implement an Internet Explorer restriction if you have total control of the client base and if Internet Explorer is your only browser, of course. See Knowledge Base article 823057 (''The Restrictions that are Available to Internet Explorer 6.0 SP1'') for more information. If you launch your page in a new window each time, the Back button on that page will be unavailable. You can also script the new window to have no toolbars.
Archos just released the new Gmini XS200 to compete with the iPod Mini. Here's a CNet review and it's already in pre-order at Amazon.com.
It's almost as small as the iPod but it has a 20GB hard disk vs iPod's 4GB. Sweet.