.net
.net
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.
Mike Krueger has created a .net wrapper for libusb library.
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 ?
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.
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. ;-)
I'm developing a .net library that contains many functions that will be used from legacy VB6 apps, in one function I need to pass an array of strings from VB6 to the .net class and since I haven't done something like that before and search the .net docs without luck, then after a lot of googling I found how to pass a string array from .net to VB6 but not the other way, after more googling I found a post in a newsgroup that suggests to use an object type parameter to receive the VB6 array and it did the trick but I would like to know if there's a better way to acomplish this...
C#
public void CreateZipFile(string zipFile,
object filesToZip) {
//
string[] listFilesToZip = (string[]) filesToZip;
...
VB6
...
Dim strFiles(2) As String
Set objZipper = New MyNamespace.FunctionsToUseFromCom
strFiles(0) = "C:\tmksrvl.exe"
strFiles(1) = "C:\setup1.log"
strFiles(2) = "C:\sqlresld.dll"
Call objZipper.CreateZipFile("C:\temp\ZipFromNet12.zip", strFiles)
...
On a previuos post I asked "Why there's a Service Pack and not (also) a new version of the .net Framework ?", well today I read a Junfeng Zhang post with the answer to my question.
The post has a link to an Alan Shi post (Alan & Junfeng belong to the Fusion team) with even more info about this subject.
A vault of them!
Great work Srinivasa.
Paschal(1)(2), Alex and others (see comments in their posts) are questioning Telligent decision to sell Community:Forums as a comercial product.
I would like to take Telligent side in this discusion.
First of all as Rob Howard clarified it doesn't mean that the source code is not available for free anymore... even further he has promised that there will always be a free version...
Did the Forums start as a community Project from zero/nada/nothing ? If my memory is not that bad I think they were a MS (or Rob Howard 's team when he worked at MS) contribution to the ASP.net community...
Was this code released under a license ? don't think so (please correct me If I'm wrong), so Rob/Telligent is free to take this code and do whatever he wants with it...
in the other side of the discussion I think that Telligent should be more explicit with the fact that Telligent can take Forums code and made a comercial/close sourced product from it. Most of us don't mind about that but it seems some people don't like this. I think they deserve at least a warning that their free contributions could be used by others (Telligent) to make money.
Anyway if there are some people that don't like what Telligent did, maybe they can take the last version of the forums code and start your own open source project (with the license they like more), and show us their real level of comminment, spend some bucks for hosting and a lot of time to coordinate such a project.
DotNetRolando.Stopwatch is my simple implementation in .net 1.x version of net 2.0's System.Diagnostics.Stopwatch. It's a very simple implementation.
You can get the code here.
- Only HighFrequency timer is implemented. A Win32Exception is thrown if the OS doesn't support HighFrequency.
- Method "GetTimeStamp" is not implemented. Still trying to figure out what this method returns.
Critics and suggestions are welcome.
I just hit with Namespace naming conflict, we decided to name a namespace like this "MyCompanyName.System", well it seems C# compiler didn't like it and try to find objects like "System.Text.StringBuilder" in "MyCompanyName.System" Namespace instead of the "System" Namespace.
The .net framework Namespace Naming Guidelines didn't mention anything about it. The C# language specification has more detail but it's somewhat confusing.
After some googling I found some posts in NewsGroups providing some workarounds but none of them satisfy me:
1) Don't use "System" in your own Namespaces names
2) Use Alias/Mask for your Namespace
using MyCompany_System = MyCompany.System; 3) Use double Alias/Mask for the System namespace (link)
using
_net_System_NameSpace = System;namespace
Belcorp.Utilities.System { using System = _net_System_NameSpace;a couple of questions left:
- Is there a more elegant workaround ?
- Has this changed in Whidbey (or fixed, I think this is a problem in .net v1.x) ?
UPDATE (Sep 17, 2004 11:45am):
It seems that also the Visual Studio 2003 IDE is affected by this problem, Intellisense is resolving against "MyCompanyName.System" Namespace instead of the "System" Namespace.
some months ago the C# team open a blog to answer C# Frequently Asked Questions, there's a post where you can post your question as a comment but the comments for that post are now closed. Is somebody of the C# team read this please let me know how to send you a question. Thanks.
Community Server Roadmap and Vision by Rob Howard
Hey Rob, Scott and Jason! do not favor forums and forget the blogs ;-) none of you blogged about these news.
earlier Wally reported that a new version of MySQL Connector/Net has been released but the link he provided doesn't provide specific details
I found a forum post with more details including the fact that it is a beta product...
but still have the doubt if it's been tested under MONO...
UPDATE (Sep 7, 2004 10:00am):
Jeff Perrin posted a comment on Wally's original post: "... this is basically the next version of the ByteFX provider (which did work under Mono, and most likely still does)...."
http://service.sap.com/connectors
from the release notes:
2. What's new in 1.0.3
======================
SAP .NET Connector 1.0.3 is a "support release" that is designed to be fully backward compatible to releases 1.0, 1.0.1 and 1.0.2. Therefore the assembly version stays the same (1.2.0.0). Only the file version is updated to 1.2.3.0.
2.1 Runtime
===========
2.1.1 Bug fixes
- Memory leaks when running RFC server programs developed with the .NET Connector
- Character conversion issues related to some codepages used in central and eastern Europe
- Other bugs
2.1.2 New Features
- Support to RFC callback has been added to the RFC client proxy based on SAPClient.
- With version 1.0.3, a .NET Connector RFC server program can also be configured as "Start on Fronend Workstation" in SM59. With earlier versions, such program can only be run as "Registered Server Program".
2.2 Design Time
===============
- Nothing
2.3 Documentation / Samples
===========================
Nothing